Jump to content
ErmaC

Clover General discussion

20,006 posts in this topic

Recommended Posts

Advertisement

I use only these on drivers64 folder for my legacy mach (sig):

MacBookPro:~ badruzeus$ cd /Volumes/EFI/EFI/CLOVER/drivers64
MacBookPro:drivers64 badruzeus$ ls
AppleImageCodec-64.efi		FSInject-64.efi
AppleKeyAggregator-64.efi	FirmwareVolume-64.efi
AppleUITheme-64.efi		SMCHelper-64.efi
MacBookPro:drivers64 badruzeus$ 

Share this post


Link to post
Share on other sites

 

 

How are you doing with the graphical glitches of the HD3000? do you have any??

I though i was the only one using an ancient cpu nowadays (as a daily driver) :)

 

DVMT does not help, also, at least on my pc, other OSes cannot boot with higher DVMT, so either MacOS is happy with any DVMT value or it just ignores the extra memory.

 

I have a lot of ram so my iHD has the max allowed shared memory available, that is 512M according to MacOS and 1.5G according to Windows (wrong?)

I m using a VRAM patch to increase the value to 1.5G.

This helped a bit.

 

I don t have persistent glitches, they seem ramdon, but actually they start only on some occasions

 

- when i reboot from linux/windows after a long session (4-5hrs +)

- when i use the iHD a lot, for ex. Maya 3d or some 2k+ youtube videos

 

So, this could be wrong but, i think that clover "poisons", or it does not clear, something related to the gpu.

 

That would explain why when i reboot from linux to MacOS i can sometimes see glithes, and i m forced to shutdown and boot MacOS directly.

 

From what i can remember i had no glitches in Mavericks and Yosemite(not sure).

 

I should probably try Mavericks + latest/older clover and see what happens when i have time.

Share this post


Link to post
Share on other sites

I though i was the only one using an ancient cpu nowadays (as a daily driver) :)

 

DVMT does not help, also, at least on my pc, other OSes cannot boot with higher DVMT, so either MacOS is happy with any DVMT value or it just ignores the extra memory.

 

I have a lot of ram so my iHD has the max allowed shared memory available, that is 512M according to MacOS and 1.5G according to Windows (wrong?)

I m using a VRAM patch to increase the value to 1.5G.

This helped a bit.

 

I don t have persistent glitches, they seem ramdon, but actually they start only on some occasions

 

- when i reboot from linux/windows after a long session (4-5hrs +)

- when i use the iHD a lot, for ex. Maya 3d or some 2k+ youtube videos

 

So, this could be wrong but, i think that clover "poisons", or it does not clear, something related to the gpu.

 

That would explain why when i reboot from linux to MacOS i can sometimes see glithes, and i m forced to shutdown and boot MacOS directly.

 

From what i can remember i had no glitches in Mavericks and Yosemite(not sure).

 

I should probably try Mavericks + latest/older clover and see what happens when i have time.

 

Thanks for your input.

 

Can you teach me how to make the VRAM patch? I have 8GB of RAM. I'd like to give it at least 1GB.

 

Is that a clover parch or I need to edit a kext?

 

Thanks in advance!

Share this post


Link to post
Share on other sites

kylon, if the issue is not clearing, you may try zeroing 0x10200000 bytes starting with 0x10000000 address. This is the area boot.efi tries to avoid for Sandy and Ivy bridge CPUs, and it may be related.

 

Are you the Lilu guy??? Thanks!

 

How do I zero that address??

 

Cheers!

Share this post


Link to post
Share on other sites

kylon, if the issue is not clearing, you may try zeroing 0x10200000 bytes starting with 0x10000000 address. This is the area boot.efi tries to avoid for Sandy and Ivy bridge CPUs, and it may be related.

Actually I using HD3000 too.

 

10.6 and 10.7 have no glitches issues on HD3000.

 

After 10.8 it have this problem and can be simply fixed by set slide=0 and work well without any glitches.

 

But after 10.11.4 this method have no function and it have more and more glitches and more and more frequently and can’t be reduced.

 

10.6 OK

10.7 OK

10.8 OK with slide=0

10.9 OK with slide=0

10.10 OK with slide=0

10.11.3 OK with slide=0

10.11.4 glitches no matter with slide value

10.12 glitches no matter with slide value

10.13 glitches no matter with slide value

 

Ps

I using legacy clover to boot on my hd3000.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

I say we try something different, protect reserved regions differently. Because macOS does not make a difference between runtime and non-runtime reserved, it only maps the runtime reserved as the same as runtime data. But I would have to think that there is a reason those reserved regions exist and according to the spec you are not supposed to use the memory regardless of the runtime flag. So maybe we should try protected runtime reserved as runtime code and non runtime reserved as runtime data?


kylon, if the issue is not clearing, you may try zeroing 0x10200000 bytes starting with 0x10000000 address. This is the area boot.efi tries to avoid for Sandy and Ivy bridge CPUs, and it may be related.

 

vit, that's only half the range when slide >= 128 for non SB and IB. What about 0x200000 to 0xFE00000? Also, this is a bad idea what if that's where the runtime was just protected? Don't want to wipe that.

 

EDIT: Oops left part of sentence out, lol.

Share this post


Link to post
Share on other sites

I have breaking news for you: Just downgraded to 10.12.6 + HFS, and guys, it is so muuch more fast than 10.13.2 + apfs. Boot is again super fast, no gui slowdowns, everything is smooth. I installed now safari tech preview to be a bit more safe against spectre. All software is working again like it should.

Share this post


Link to post
Share on other sites

Question:

 

I saw at around 750 page that you where talking about patches for Pentium and integrate them directly into Clover version 41xx. Does that happend ? I am asking because I have 2 patches in my config.plist made by vit9696 and Sherlocks and I wanna know if I can remove them or not:

 

Find: b9a00100 000f32

Replace: b9a00100 0031c0

 

Find: 89d804c4 3c22

Replace: 89d804c6 3c22

 

I have the Pentium G3220.

Share this post


Link to post
Share on other sites

Question:

 

I saw at around 750 page that you where talking about patches for Pentium and integrate them directly into Clover version 41xx. Does that happend ? I am asking because I have 2 patches in my config.plist made by vit9696 and Sherlocks and I wanna know if I can remove them or not:

 

Find: b9a00100 000f32

Replace: b9a00100 0031c0

 

Find: 89d804c4 3c22

Replace: 89d804c6 3c22

 

I have the Pentium G3220.

 

These patches in clover:

#1

#2

Use KernelXCPM key in KernelAndKextPatches.

 

Share this post


Link to post
Share on other sites

These patches in clover:

#1

#2

Use KernelXCPM key in KernelAndKextPatches.

 

 

Thank you ! I deleted the kernel patches and it's working ! 

 

Anyway can somebody take a look on my DSDT and other stuff ? I am asking because the sound via HDMI works only after sleep. Like after sleep the sound works but before it doesn't...

 

https://drive.google.com/open?id=18YGCj5Z3j8cehMOChGtckap0uWmQ6tjA

Share this post


Link to post
Share on other sites

@apianti

 

Tested new OsxAptioFix2Drv-64.efi on my NUC6 Skull Canyon (NUC6i7KYK) with 10.13.2.

Tested by merging in changes to my own Clover fork.

It booted no problem and was able to eliminate EmuVariableUefi-64.efi and still have working NVRAM.

 

Will test on other computers in the coming days.

 

But since the new OsxAptioFix2Drv-64.efi is not working for everyone, perhaps it should be renamed OsxAptioFix3Drv-64.efi (or some other name) and original behavior of OsxAptioFix2Drv-64.efi retained.

Not to mention undoing the changes in OsxAptioFixDrv-64.efi that prevent it from being used at all (as you implied in a previous post).

Share this post


Link to post
Share on other sites

@apianti

 

Tested new OsxAptioFix2Drv-64.efi on my NUC6 Skull Canyon (NUC6i7KYK) with 10.13.2.

Tested by merging in changes to my own Clover fork.

It booted no problem and was able to eliminate EmuVariableUefi-64.efi and still have working NVRAM.

 

Will test on other computers in the coming days.

 

But since the new OsxAptioFix2Drv-64.efi is not working for everyone, perhaps it should be renamed OsxAptioFix3Drv-64.efi (or some other name) and original behavior of OsxAptioFix2Drv-64.efi retained.

Not to mention undoing the changes in OsxAptioFixDrv-64.efi that prevent it from being used at all (as you implied in a previous post).

Or it can be renamed as LowMemFixup.efi because this problem is a common problem not only in ami aptio bios.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

What about naming it then like:

OsxAptioFixDrv-1011up-64.efi
OsxAptioFixDrv-1010down-64.efi

Or similar...? I don't find the numbering 1,2,3 very useful for non-hackers.

No, these names are historical. 

Fix1 is more advanced.

Fix2 is simplified but supported hibernation.

 

 

@apianti

 

Tested new OsxAptioFix2Drv-64.efi on my NUC6 Skull Canyon (NUC6i7KYK) with 10.13.2.

Tested by merging in changes to my own Clover fork.

It booted no problem and was able to eliminate EmuVariableUefi-64.efi and still have working NVRAM.

 

Will test on other computers in the coming days.

 

But since the new OsxAptioFix2Drv-64.efi is not working for everyone, perhaps it should be renamed OsxAptioFix3Drv-64.efi (or some other name) and original behavior of OsxAptioFix2Drv-64.efi retained.

Not to mention undoing the changes in OsxAptioFixDrv-64.efi that prevent it from being used at all (as you implied in a previous post).

 

I agree there must be Fix3 retaining old Fix1 and Fix2.

And see new one      AptioMemoryFix    

Share this post


Link to post
Share on other sites

Hey slice,

can I add new entries to a plist, using the kext patcher in clover? I read somewhere it only can replace 1:1 lengths?

More specific: How do I replace a

      <key>UnifiedSleepSliderPref</key>
      <true/>

to

      <key>UnifiedSleepSliderPref</key>
      <false/>

Also, does it work with plugins of kexts?

 

Path is:

/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/Mac-27ADBB7B4CEE8E61.plist

(For iMac14,2)

Share this post


Link to post
Share on other sites

Hey slice,

 

can I add new entries to a plist, using the kext patcher in clover? I read somewhere it only can replace 1:1 lengths?

 

More specific: How do I replace a

      <key>UnifiedSleepSliderPref</key>
      <true/>

to

      <key>UnifiedSleepSliderPref</key>
      <false/>

Also, does it work with plugins of kexts?

 

Path is:

/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/Mac-27ADBB7B4CEE8E61.plist

(For iMac14,2)

 

Only info.plists of kexts and a find/replace situation. If the above string were on a info.plist the way it could work is to select the text to replace with an Hex editor plus an aditional byte to replace a string of the same length because false is larger than true.

Share this post


Link to post
Share on other sites

Hm, ok, I geddit: The replace is like that, because it replaces on the memory of the kext cache, so no real xml/plist logic inside, just raw search/replace...

 

I could remove one tab then...

3c6b6579 3e556e69 66696564 536c6565 
070536c6 96465725 07265663 c2f6b657 
093e0a20 20202020 203c7472 75652f3e

to

3c6b6579 3e556e69 66696564 536c6565
070536c6 96465725 07265663 c2f6b657
093e0a20 20202020 3c66616c 73652f3e

So in clover config:

		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>unified powercontrol off</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				PGtleT5VbmlmaWVkU2xlZQBwU2xpZGVyUHJlZjwva2UH
				CT4KICAgICAgPHRydWUvPg==
				</data>
				<key>InfoPlistPatch</key>
				<true/>
				<key>Name</key>
				<string>X86PlatformPlugin.kext</string>
				<key>Replace</key>
				<data>
				PGtleT5VbmlmaWVkU2xlZQcFNsaWRlclByZWY8L2tlcJ
				PgogICAgIDxmYWxzZS8+
				</data>
			</dict>
		</array>

But how do I address the Resource dir inside that kext? Since the sub path is:

IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources/Mac-27ADBB7B4CEE8E61.plist

How to target it? Just Name = "X86PlatformPlugin.kext"? EDIT: No, that does not work. Then "com.apple.driver.X86PlatformPlugin" ? Or the outer kext, "IOPlatformPluginFamily.kext" ?

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   1 member

  • Similar Content

    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI CLOVER Z390 DESIGNARE.zip
       
      ---OPENCORE FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI OPENCORE Z390 DESIGNARE.zip
       
      ---DSDT patch requests is here---
       
      https://olarila.com/forum/viewtopic.php?f=19&t=1131
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      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 kylon
      Cloud Clover Editor is an open source application that allows you to manage various Hackintosh Bootloaders configs everywhere.

      Open Cloud Clover Editor
       
      Cloud Clover Editor Wiki
      Cloud Clover Editor Sources
       
       
      Features
      Supports Clover EFI, Ozmosis, Chameleon, OpenCore GUI and Text Editor Mode CCE Bank Mobile friendly  
      Officially supported browsers
      Chrome 42+ Microsoft Edge 14+ Firefox 39+ Safari 10+ Opera 29+ Opera Mobile 12+ Chrome for Android 75+ Firefox for Android 67+  
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor  (Discontinued) crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support  
      Please let me know if i forgot you!
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) ->  Link download
       Può essere solo aggiunto manualmente scaricando dal link sopra e collocandolo nella rispettiva cartella
       NOTA: in questo caso non selezionare nessun OsxAptioFixDRV durante l'installazione di clover oppure rimuovetelo                        successivamente. 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
       
       
       
       
       
       
       
       
       
       
       
       
    • By Alesss
      Good morning,
       
      I've the following pieces of hardware:
      - i7 6700K
      - GTX 1080
      - Asus Z170 Deluxe
      - NVME hard drives
       
      Yesterday I've successfully completed a High Sierra installation (I can't migrate to Mojave due to missing NVIDIA web drivers) but the system (even though it works correctly) seems to show a kernel panic at every shutdown/reboot.
       
      Please find the RunMe.app report attached.
       
      A couple of notes:
      - I've installed the audio kexts through the acidanthera AppleALC procedure
      - I've generated the SSDT with pikessdt script
      - Nvidia web drivers have been installed with the vulgo/webdriver.sh script that requires the WhateverGreen and the ngfxcompat=1 boot argument
      - AirportBrcmFixup.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext have been used to unlock the full potential of the integrated Wi-Fi card
      - I've tried to clean nvram and motherboard CMOS with no avail
      - I've tried to update Clover to the latest version but it always results in an unbootable system
       
      It's a pity because everything seems to work correctly (USB ports, graphics, Wifi card, Continuity and so on. I haven't tried sleep but I don't use it anyway ) but this crash is fairly annoying.
       
      Thank you very much,
      Alesss
       
      Send me Ales-iMac.zip
    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
×