Jump to content
DaHarry

Intel i9 9900k - Gigabyte Z390 Ultra - VirtualSMC vs. FakeSMC

7 posts in this topic

Recommended Posts

I have installed Hackintosh on to my System, but the CPU cooler is obviously louder then on Windows.

I am using right now VirtualSMC.kext, but since FakeSMC provides temperature measurement tools, and VirtualSMC not, I asked my self if that might be a hint for my loud cooler?

  1. My question, has somebody tried maybe both and even compared them? And is FakeSMC maybe less noisy?

  2. Is it enough to just mount EFI partition, and delete the VirtualSMC.kext and put instead FakeSMC.kexts ? Without any fancy kext installation tool or terminal commands, just replace files and restart in enough?

My System:

Mainboard: Gigabyte Aorus Z390 Ultra

CPU: Intel i9 9900k

CPU Cooler: BeQuiet! Dark Rock 4

GPU: Vega 64

Ram: 2x16GB Corsair 3200

SSD: 1TB Adata M.2

 

The Tutorial i have used - https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md

 

Really works like a charm besides, the more noisy cooler, which i bought because it is extra quietly.

I asked first at tonymac's forum, but they deleted the post because I haven't used their tool, really disgustig.. I really hope to never use their tools, and I hope here the information freedom is more respected.

#f. tonyhoremacs

Edited by DaHarry

Share this post


Link to post
Share on other sites
Advertisement
23 hours ago, DaHarry said:

My question, has somebody tried maybe both and even compared them? And is FakeSMC maybe less noisy?

Tried both. No real difference. Its just up to what you "prefer". I use Fakesmc and extensions on my z390 Aorus Elite and it works flawless. 

I use virtualSMC and its extensions on my Dell 7559 laptop and it works flawless. I notice SMCBatteryManager works better for my laptop than other choices. 

Just personal preference. 

Share this post


Link to post
Share on other sites

Ok, I realized first now that my graphics card fan is the noisy one.

I swapped virtualSMC with fakeSMC, and run HWMonitor and my CPU Cores are all around 32° but my graphics card is claimed to be 127°.

That is really strange and seems to be even dangerous.

I thought Vega64 would be compatible out of the box?

Share this post


Link to post
Share on other sites
6 hours ago, DaHarry said:

Ok, I realized first now that my graphics card fan is the noisy one.

I swapped virtualSMC with fakeSMC, and run HWMonitor and my CPU Cores are all around 32° but my graphics card is claimed to be 127°.

That is really strange and seems to be even dangerous.

I thought Vega64 would be compatible out of the box?

I have the same issue, let me know if you figure out, how to fix this. However, I don't think that is the 'real' temperature.

Share this post


Link to post
Share on other sites
On 2/3/2019 at 4:15 PM, tikizondo94 said:

Tried both. No real difference. Its just up to what you "prefer". I use Fakesmc and extensions on my z390 Aorus Elite and it works flawless. 

I use virtualSMC and its extensions on my Dell 7559 laptop and it works flawless. I notice SMCBatteryManager works better for my laptop than other choices. 

Just personal preference. 

 

hello corsair mp500 What is the read / write speed of NVME M.2? I have the same model as the read / write speed is very slow.

 

 

Ekran Resmi 2019-02-11 22.41.12.png

Share this post


Link to post
Share on other sites
1 hour ago, lahana1 said:

 

hello corsair mp500 What is the read / write speed of NVME M.2? I have the same model as the read / write speed is very slow.

 

 

Ekran Resmi 2019-02-11 22.41.12.png

Mine seems to be pretty snappy. I did have issues before when i had to many Drives hooked up. It seemed to slow my write speeds down to a solid 200mb sec. Also watch for thermal throttling with NVMe drives. Heat is not there friend. 

Screen Shot 2019-02-11 at 3.51.51 PM.png

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By MaLd0n
      ---INSTALLATION TUTORIAL---
       
      ---Original Post---
      https://olarila.com/forum/viewtopic.php?p=77102#p77102
       
      ---CLOVER FOLDER---
       
      CLOVER.zip
       
      --MOBO
      GigaByte Z390 M Gaming



      --PROCESSOR
      Intel Core i9-9900K


      --COOLER
      CoolerMaster MasterLiquid ML120R RGB


      --MEMORY
      Corsair Dominator Platinum 16GB (2 x 8GB)


      --GPU
      Sapphiretech Radeon RX 590 8 GB GDDR5


       
      --SSD
      Samsung 970 EVO NVMe M2 Flash Drive


      --POWER SUPPLY
      EVGA 750 N1, 750W


      --WIRELESS
      TP-Link Archer T9E


      --BLUETOOTH
      Orico BTA-403


      --CASE
      Thermaltake View 21 Tempered Glass Edition


      --DSDT Patches--
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE 10 ID -DMAC -REMOVE 22K LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM / REAL TIME CLOCK -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -MIKEY -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -OPERATION REGION GPIO -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES  
      --SCREENSHOTS--





























      --BruceX--
       
      --USB-C-- test with SanDisk Ultra USB-STICK 128gb


       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By chan29ster
      Hello 
       
      My Config is
       
      Intel core i5 9400f
      Gigabyte z390 aorus Pro Wifi Motherboard (with latest BIOS version F9a)
      8gb x 2 Corsair Vengeance Ram 3000 Mhz
      Zotac GTX 1060 Amp! Edition 6gb (Dual Fan)
      1 TB Baracuda Hard Disk
      Corsair Spec Delta Atc Cabinet
      TP-Link w832n USB Wifi Dongle for wifi 
       
      macOS Sierra 10.12.6 (16G29)
       
      I am able to get onboard audio, bluetooth, ethernet and all USB ports working.
       
      But as I install Nvidia web drivers and input boot flag "nada_drv=1" my screen gets stuck at 
       
      IOConsoleUsers : time(0) 0->0, Lin 0, lik 1
      IOConsoleUsers : gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0
       
      Please help me 
       
       
      Thanks
    • By 1Ale1
      Ciao a tutti, ultimamente ho deciso di mettermi al lavoro e fare un investimento a lungo termine comprando un fisso che ho assemblato pezzo dopo pezzo leggendo numerosi forum per essere bene informato sul miglior hardware che potessi ottenere per un Hackintosh ottimizzando al meglio i costi: ho finito così per comprare:
       
      Hardware:
       
       
      -Motherboard: Gigabyte Z390 Aorus Pro (Rev 1.0)
      -CPU: Intel i7 9700k raffreddato a liquido (CoffeLake)
      -GPU: AMD Radeon RX580 (avendo letto le eccellenti prestazioni a ottimo prezzo per MacOS)
      -RAM: 32GB DDR4 Crucial Ballistix Sport LT (4x8GB 3000MHz)
      -NVMe SSD Samsung 970 Evo 250GB M.2 dedicato solo a MacOS, nel secondo slot della Mobo M.2 avrei poi messo un Western Digital Blue da 250GB con Windows 10 su metà disco e per l'altra metà il Debian che sto utilizzando adesso
       
       
      Poi mi sono messo subito al lavoro per cercare di far partire questo benedetto MacOs su una macchina non ufficiale, ho tovato quindi questa guida su GitHub che era molto simile alla mia configurazione:
       
      https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md
       
      Dopo aver fatto partire una macchina virtuale per configurare la USB come comunemente viene fatto, scaricando l'applicazione e facendo il "burn/copia dei file" di macOS su pennetta esterna rendendola bootabile solamente da un pc ufficiale mac, sono passato alla configurazione di Clover (l'EFI installer, cartella che allegherò qui sotto, ma prima leggete il problema): Ho messo i driver necessari, mettendo quelli che lui menzionava sotto la sezione "building the usb installer"
       
      https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/building-the-usb-installer
       
       
      Install Clover for UEFI booting only
      Install Clover to the ESP
      Under Drivers64UEFI:
      AptioMemoryFix (the new hotness that includes NVRAM fixes, as well as better memory management) (che poi ho dovuto rimuovere, leggi sezione https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md#fixing-kernel-panics-at-rebootshutdown)
      VBoxHfs-64.efi (or HFSPlus.efi if available) - one of these is required for Clover to see and boot HFS+ volumes. If you see the option to enable it in the installer, make sure it's selected - if you don't see it in the installer, verify that one of them exists in the EFI -> CLOVER -> drivers64UEFI folder
      ApfsDriverLoader - (Available in Dids' Clover builds - or here) this allows Clover to see and boot from APFS volumes by loading apfs.efi from ApfsContainer located on block device (if using AptioMemoryFix as well, requires R21 or newer)
       
      applicando piccole modifiche a causa di un errore già riportato da questa persona che ha scritto la guida di GitHub di sostituire AptioMemoryFix-64 (dalla cartella EFI/EFI/CLOVER/driver64UEFI) con OsxAptioFix2Drv-free2000, questa infatti riportava  quanto segue dopo aver detto di aver sostituito AptioMemoryFix-64.efi con OsxaptioFix2Drv-free2000:
       
      "I am told that there are downsides (that I don't fully understand yet) to using OsxAptioFix2Drv-free2000, so do this at your own risk."
       
      Ho configurato poi il config.plist
       
      Come diceva lui, partendo da questo file: https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/config.plist-per-hardware/coffee-lake e applicando le modifiche che sotto ha descritto, del tipo:
       
      Open coffeelake_sample_config.plist with Clover Configurator (right click → Open With → Clover Configurator)   In SMBIOS: - Click the button with an up/down arrow (middle right). Chose iMac18,3. This is important since we'll be connecting our monitor to the RX580. The HDMI port on our motherboard is NOT yet working for Hackintoshes. - Make sure the serial number generated is an iMac (mid-2017) by clicking Model Lookup. - Ensure that Check Coverage reports that the serial is NOT valid. You don't want to use somebody else's serial number. - While you're here, copy your Board Serial Number to your clipboard. You'll need it soon.
      In Rt Variables: Paste your Board Serial Number in the MLB field. Set CsrActiveConfig to 0x0 which enables SIP for extra security. This should work just fine for a Vanilla Hackintosh install and is how genuine Macs ship. In Boot: Change the Custom Flags to: shikigva=40 uia_exclude=HS14 (this disables onboard Bluetooth since we'll be using an external Broadcom Wi-Fi/Bluetooth adapter) In ACPI: Click List of Patches and enable the following: Change GFX0 to IGPU In Devices: Set Inject to 16. Now to enable our headless iGPU, we need to fake the device id. To do so, Click Properties, select PciRoot(0x0)/Pci(0x2,0x0). Then, click the + button to add a property. Add the following: Property Key: device-id Property Value: 923E0000 Value Type: DATA Click the Export Configuration button (bottom left), then Save As config.plist. Copy your newly generated config.plist to /EFI/CLOVER/ on your bootable USB key.  
      Impostazioni BIOS
       
      E avendo settato nel BIOS le impostazioni che questa perona configliava all'inizio della guida,                       (N.B. la mia versione di Bios è l'ultima, F7 https://www.gigabyte.com/Motherboard/Z390-AORUS-PRO-rev-10#support-dl-bios) (a quanto risulta il giorno 7.01.2019)
       
      Load Optimized Default Settings Peripherals → USB Configuration → XHCI Hand-off : Enabled Chipset → Internal Graphics : Enabled (important for Quicklook/Preview) Please note that we will be using our internal GPU in headless mode only and this guide assumes that. This is how an iMac18,3 (what we're basing our build on) behaves. That's it! I literally didn't change anything else and it just worked.
       
      Anche per me ha funzionato. Comunque lui riportava ulteriori settaggi, aggiungendo:
       
      However, these are settings that are generally recommended. Your mileage may vary:
       
      BIOS → Fast Boot : Disabled BIOS → LAN PXE Boot Option ROM : Disabled BIOS → Storage Boot Option Control : UEFI Peripherals → Trusted Computing → Security Device Support : Disable Peripherals → Network Stack Configuration → Network Stack : Disabled Peripherals → USB Configuration → Legacy USB Support : Auto Peripherals → USB Configuration → XHCI Hand-off : Enabled (Extremely important) () Chipset → Vt-d : Disabled (non l'ho messo e parte a volte, quindi penso che se parte non ha una importanza così rilevante) Chipset → Wake on LAN Enable : Disabled (era già così) Chipset → IOAPIC 24-119 Entries : Enabled  
       
      Il sistema è partito e soltanto alcune volte dava il seguente errore:
       
      Error allocating 0x11996pages at 0x000000001d453000 alloc type 2
      Couldn't allocate runtime area.
       
      Credo che sia questo piccolo problema: la NVRAM.
      Non riesco bene a capire dove cercare per sapere con esattezza se è supportato nativamente o meno. Ho cercato di informarmi, voi potreste dirmi se è vero?
      Premendo poi Ctrl+Alt+Canc riavviavo e selezionando da Clover l'NVMe interno partiva senza dare questo errore, per cui il kernel non trova spazio perché la memoria Non Volatile ad accesso Randomico è troppo frammentata, come
       
      Questa guida riportava:
       
      Primo post:
      https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/
       
      Post aggiornato nel 2016:
      https://nickwoodhams.com/x99-hackintosh-osxaptiofixdrv-allocaterelocblock-error-update/
       
      Mi sono letto tutto e ho capito che lui applicava anche delle modifiche al file: "Changes to OsxLowMemFixDrv-64.efi were simply editing 0x10000000 to 0x20000000."
       
      Ho quindi seguito il suo consiglio di mettere OsxAptiofix Emuvariable 64 e Test2-2016.efi (che lui aveva creato) ma il problema sembrava persistere, più raramente
       
      La mia cartella driver64UEFI di ora
       
      Dopo aver trovato una strada senza soluzoni anche lì mi sono rivolto a degli amici, e di questo errore ne ho parlato anche con utenti del gruppo Telegram "Hackintosh Italia" che sono stati e ancora sono molto gentili ad aiutarmi spiegandomi che si tratta di un problema di NVRAM, che nel mio caso, avendo installato questi .efi file nella cartella EFI/EFI/CLOVER/driver64UEFI (che ancora è cosi attualmente, oscillando tra couldnt allocate runtime area (anche dopo aver definitivamente staccato la corrente dopo aver spento il PC per capire se poteva aiutare) e a volta anche nessun errore)
       
       
      -ApfsDriverLoader-64.efi
      -DataHubDxe-64.efi
      -EmuVariableUefi-64.efi
      -FSInject-64.efi
      -HFSPlus-64.efi
      -NTFS-64.efi
      -NvmExpressDxe-64.efi
      -OsxAptioFix2Drv-free2000.efi
      -PartitionDxe-64.efi
      -UsbKbDxe-64.efi
       
      In più ho aggiunto gli RC Scripts (come mi è stato consigliato dai membri del gruppo telegram) sul disco interno in cui mac è installato.
       
      Togliendo quindi qualsiasi test.efi o test2- 2016.efi ed ascoltando chi ne sapeva di più. Ora mi trovo a dover affrontare diverse volte questo errore dovendo riavviare per risolverlo, cosa che mi fa dedurre che Osxaptiofix2 2000 sia un po' instabile nel pulire la NVRAM prima di avviare la macchina/ allo spegnimento di questa.
      Questo problema di couldnt allocate runtime area persiste sebbene prema F12 dalla schermata di Boot di Clover.
       
      Vi chiedo gentilmente una mano, inoltre mi è stato detto che siccome il sistema da:
       
      -"3.6 GHz unknown nella sezione "Processor"
      -non riconosce la RAM con un Vendor ID? (del tipo Ballistix dovrebbe essere?)
       
       
      Serve di rivedere il config.plist che ho creato, rivedere i DSDT e gli efi? sono a posto?, (mi hanno detto che gengik84 fare, ma accolgo volentieri l'aiuto di tutti) ,  vi mando una foto della schermata di "About this Mac" e della EFI in allegato. Quello che farò sicuramente mentre attendo vostre risposte è il downgrade da 10.14.3 Beta a 10.14.2, l'upgrade l'ho fatto pensando che magari avrei aggiustato qualcosa, ma l'errore come lo dava prima lo dà ora, non credo che questo cambi molto le cose in gioco. Comunque è meglio non essere in Beta per aggiustare gli errori.
       
       
      Grazie mille per essere arrivato a leggere fino a questo punto, lo apprezzo molto.
       
       
      Per la cartella EFI: sono 22MB zippati, in allegato non entrano...
       
      https://drive.google.com/open?id=106jXkDB0Id045lzIIzAn9F5MwnzWFv3X
       

       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       

       
       
       
       



    • By RSN
      Hi Everybody.
       
      Success for the Z390 Gigabyte. Specs follow:
       
      16GB DDR4 Corsair
      i7-9700 CPU
      Asus Radeon 580
      SSD 1TB
      SSD 512GB
      SSD 128GB
       
      How I did it.
       
      I had a working HighSierra and boldly just booted in the new MB+CPU. jaja. Well, it did not work. Googled and found somebody had a Z370 and posted his EFI folder. Saved my EFI and replaced it with the Z370 one.
      Boldly, again, rebooted and ... it worked, mostly!!!!. So now I am in High Sierra with my new Hackintosh. Cool. Some sound problem, long story short, there is a kext, replaced and SOUND.
       
      What works
      Graphics, not the built in HDMI, but the Radeon card. ALL ports, I have 4 screens
      USBs all, 3.0,3.1,2.0
      Ethernet port
      Sound with a new kext
      Track Pad with bluetooth dongle
      Wifi external Card
       
      What does not work
       
      Built In HDMI.
      Wifi Built In. I guess it will NEVER work. To "windows" style to ever be used by Apple.
      Built In Bluetooth which is related to the WiFi above.
       
      Attach is the Clover Folder of the EFI (too big to attach). Has the required Kexts and driveruefi
       
      Migrate to Mojave
      Well, incredible as it may sound, just double click on the Install Mojave OSX, you need to download, and just go thru the process. Just one loss, the external WiFi, seems it is not supported by Mojave. Copied from HighSierra the IO802...kext and the IONetworkFamily.kext. Worked.
       
      Clean Install Mojave
       
      Many tuts about it, used one found in youtube, https://www.youtube.com/watch?v=VdRSYogDygs, which uses a batch process to create the usb installer, etc. Follow it. Simple.
      Again, use the kexts given in the Clover folder attached. One finished with creating the usb installer, open the EIF partition and change the Clover folder to this one.
       
      Install New Mojave with USB Installer
      Do the process of installing and when finished install the Clover boot loader (watch the video). After that again change the Clover folder in the EFI partition with this one.
       
      Results
       
      1) Migrate from HighSierra to Mojave. Just change the Clover folder in the EFI partition and Install OSX Mojave app.
      2) Mojave Installer. Create USB installer, install Clover boot loader and change Clover folder in EFI partition.
      3) New Mojave Install. Install via Mojave Installer, install Clover boot loader and change Clover folder in EFI.
       
      Hope it helps.
       
      CLOVER.zip
    • By shmn
      Hey guys, my hack gets stuck at the attached screen, saying the 'VirtualSMC EFI module is broken' and it's waiting on some boot media. It does boot once in a while, but I cannot reproduce what makes it work, removing all USB devices doesn't help for instance. I know this seems to be a common issue, but the solutions I found didn't help.
      Please find attached the screenshot and my Clover folder. Any support much appreciated! (:

      CLOVER.zip
×