Jump to content
ErmaC

Clover General discussion

18,966 posts in this topic

Recommended Posts

Are these 2 NVRAM vars created by BootChimeCfg (red rectangles)?

Correct me if I'm wrong; can we run eg. this command via Terminal w/o Shell > fs0:\efi\clover\tools\bootchimecfg then?

sudo nvram specialbootdevice blah blah blah

Thanks.

 

 

 

nvram -p.png
[/spoler]

 

#EDIT: ..and I have this on my preboot logs with r4847:

 

preboot.png

 

nvram_dmpstore_all_a43sj.txt.zip

Edited by Badruzeus

Share this post


Link to post
Share on other sites
Advertisement
14 hours ago, ellaosx said:

I get both if i combine slice & Goldfish64

What do you mean both? Could you tell me exactly what you did?

 

EDIT:
I added BootChimeDxe and got startup sound but immediately got red screen of death.

Edited by pkdesign

Share this post


Link to post
Share on other sites

 

I am able to get the test sound from BootChime.Cfg.efi in shell but it doesn't play at boot and it doesn't play under the Startup sound options in Clover. My system is UEFI based.

 

I am using

 

AudioDxe-64.efi from v2.4k_r4848 in drivers64UEFI

 

and

 

BootChime.Cfg.efi and BootChimeDxe.efi from Goldfish64 AudioPKG in tools.

 

How to further trouble-shoot?

 

 

Share this post


Link to post
Share on other sites
6 minutes ago, Tobiko said:

 

I am able to get the test sound from BootChime.Cfg.efi in shell but it doesn't play at boot and it doesn't play under the Startup sound options in Clover. My system is UEFI based.

 

I am using

 

AudioDxe-64.efi from v2.4k_r4848 in drivers64UEFI

 

and

 

BootChime.Cfg.efi and BootChimeDxe.efi from Goldfish64 AudioPKG in tools.

 

How to further trouble-shoot?

 

 

 

Do you put sound file in your theme folder? I think you do not use BootChimeDxe.efi (it's a driver not a tool). Some others members can help you better than me.

 

Take a look for parameters:

 

Share this post


Link to post
Share on other sites

Hi,

 

 

 

Thanks. I saw that thread. I used this as a guide but using the different file versions I mentioned. I use the Clovy theme which has a sound.wav in it. I also tried adding the sound.wav Slice provided to /EFI. 

 

I tried it on my desktop and it worked fine using BootChime.Cfg.efi from GoldFish64, the AudioDXE-64 from Clover and the Clovy theme which has a sound.wav. 

 

So on my laptop which is where this all started, I removed BootChimeDxe.efi rebooted, ran BootChime.Cfg.efi again it still worked from there. Cleared the NVRAM, ran BootChime.Cfg.efi and set up the device and volume again, rebooted a couple of times but still no luck. I even wiped clover and started fresh even recompiling the AudioPKG still not working on the Laptop. Just from the shell. 

Edited by Tobiko
tried additional steps

Share this post


Link to post
Share on other sites
58 minutes ago, Sherlocks said:

@vit9696

thank you for r4846 commit.

this is very great fix. i had problem unknown panic on sandy bridge laptop until this commit.

there is no more instant reboot issue

thanks :)

@Sherlocks Wait, Sandy? Seems no problem here.. but, my Mojave is using HFS+ since 10.14 till 10.14.3 #btw

Or could bcoz something else (we have diff. specs but CPU #LoL )

 

Oh hai, you didn't response my proposition yet since last year?

Spoiler

--- /Users/badruzeus/udk/UDK2018/Clover/rEFIt_UEFI/entry_scan/loader.c	2018-12-21 20:51:48.000000000 +0700
+++ /Users/badruzeus/src/edk2/Clover/rEFIt_UEFI/entry_scan/loader.c	2019-01-17 22:37:40.000000000 +0700
@@ -102,6 +102,9 @@
   { L"\\EFI\\goofiboot\\goofibootx64.efi", L"Solus EFI boot menu", L"solus,linux", "Solus" },
   { L"\\EFI\\centos\\grubx64.efi", L"CentOS EFI boot menu", L"centos,linux", "CentOS" },
   { L"\\EFI\\pclinuxos\\grubx64.efi", L"PCLinuxOS EFI boot menu", L"pclinux,linux", "PCLinux" },
+  { L"\\EFI\\neon\\grubx64.efi", L"KDE Neon EFI boot menu", L"neon,linux", "KDE Neon" },
+  { L"\\EFI\\MX18\\grubx64.efi", L"MX Linux EFI boot menu", L"mx,linux", "MX Linux" },
+  { L"\\EFI\\parrot\\grubx64.efi", L"Parrot OS EFI boot menu", L"parrot,linux", "Parrot OS" },
 #else
   { L"\\EFI\\grub\\grub.efi", L"Grub EFI boot menu", L"grub,linux" },
   { L"\\EFI\\Gentoo\\grub.efi", L"Gentoo EFI boot menu", L"gentoo,linux", "Gentoo" },
@@ -127,6 +130,9 @@
   { L"\\EFI\\goofiboot\\goofiboot.efi", L"Solus EFI boot menu", L"solus,linux", "Solus" },
   { L"\\EFI\\centos\\grub.efi", L"CentOS EFI boot menu", L"centos,linux", "CentOS" },
   { L"\\EFI\\pclinuxos\\grub.efi", L"PCLinuxOS EFI boot menu", L"pclinux,linux", "PCLinux" },
+  { L"\\EFI\\neon\\grub.efi", L"KDE Neon EFI boot menu", L"neon,linux", "KDE Neon" },
+  { L"\\EFI\\MX18\\grub.efi", L"MX Linux EFI boot menu", L"mx,linux", "MX Linux" },
+  { L"\\EFI\\parrot\\grub.efi", L"Parrot OS EFI boot menu", L"parrot,linux", "Parrot OS" },
 #endif
   { L"\\EFI\\SuSe\\elilo.efi", L"OpenSuse EFI boot menu", L"suse,linux" },
 };

 

 

Thank you before.. (y)

loader.c.patch.zip

Share this post


Link to post
Share on other sites
On 1/16/2019 at 4:58 AM, Badruzeus said:

Are these 2 NVRAM vars created by BootChimeCfg (red rectangles)?

Correct me if I'm wrong; can we run eg. this command via Terminal w/o Shell > fs0:\efi\clover\tools\bootchimecfg then?


sudo nvram specialbootdevice blah blah blah

Thanks.

 

No, those are the macOS variables. These are the variables:

Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 3C                                               *<*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Index' DataSize = 0x08
  00000000: 00 00 00 00 00 00 00 00-                         *........*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Device' DataSize = 0x2E
  00000000: 02 01 0C 00 D0 41 03 0A-00 00 00 00 01 01 06 00  *.....A..........*
  00000010: 00 1B 03 0A 18 00 EB 3F-00 A9 06 D8 DB 41 A4 91  *.......?.....A..*
  00000020: 54 05 FE EF 46 C3 00 00-00 00 7F FF 04 00        *T...F.........*

 

Share this post


Link to post
Share on other sites

Error building 4848 with GCC 

/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c:36:15: error: type of 'EmbeddedSound' does not match original declaration [-Werror=lto-type-mismatch]
 extern UINT8 *EmbeddedSound;
               ^
/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/sound.c:1:7: note: 'EmbeddedSound' was previously declared here
 UINT8 EmbeddedSound[] = {
       ^
lto1: all warnings being treated as errors
lto-wrapper: fatal error: /Users/stlvnub/src/opt/local/cross/bin/x86_64-clover-linux-gnu-gcc returned 1 exit status
compilation terminated.
/Users/stlvnub/src/opt/local/cross/lib/gcc/x86_64-clover-linux-gnu/8.1.0/../../../../x86_64-clover-linux-gnu/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
make: *** [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit/DEBUG/CLOVER.dll] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
	/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/refit.inf [X64, GCC53, RELEASE]

- Failed -
Build end time: 16:58:25, Jan.18 2019
Build total time: 00:00:43


o_Ops, ./ebuild.sh exited with error(s), aborting..

 

Share this post


Link to post
Share on other sites
On 1/16/2019 at 2:53 AM, pkdesign said:

I'm guessing us users with BIOS (non UEFI) motherboards are out of luck? I get sound when in Clover Shell but not during boot.

 

The boot chime works perfectly using AudioDXE.efi and BootChimeDXE.efi in the drivers64 folder. Those (and only those) two drivers are enough to get the chime going when the macOS boot entry is selected in Clover.

 

The only annoyance for me is that Clover takes 3 extra seconds to start. Hopefully that will be slightly optimized in the future.

 

PS. My laptop does have UEFI but its disabled. I'm using legacy boot.

 

Share this post


Link to post
Share on other sites

I'm having a hard time setting my DefaultVolume in my config.plist, could someone please help me take a look at this bootlog and tell me what to put in the DefaultVolume field? I have tried reversing the endianness as someone suggested on another post ("C4B2367B74CD456F9E87FE3696F379E0"), as well as "Macintosh HD" and "7B36B2C4CD746F459E87FE3696F379E0" but it doesn't seem to work. Specifically, I am trying to set volume 09 as the boot default. I am able to set another drive without issue, so I don't think it's my config that is wrong...

 

1:784  0:002  - [08]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,AB2E508E48943E47B77B4294154D845B)
1:784  0:000          hiding this volume
1:784  0:000  - [09]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,7B36B2C4CD746F459E87FE3696F379E0)
1:784  0:000  - [10]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,085E15BDE052F446BB30B7D3714422FC)
1:784  0:000          hiding this volume
1:784  0:000  - [11]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,749023097C268C4D88A57ED372FE4D36)

--- SNIP ---

2:076  0:043  - [08]: 'Preboot', hidden
2:076  0:000  - [09]: 'Macintosh HD'
2:223  0:147          AddLoaderEntry for Volume Name=Macintosh HD
2:257  0:033      Check if volume Is Hibernated:
2:257  0:000      Check sleep image 'by signature':
2:297  0:040      read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success
2:297  0:000      using default sleep image name = \private\var\vm\sleepimage
2:329  0:031      sleepimage not found -> Not Found
2:329  0:000      hibernated: no - sign
2:333  0:004          [!] Icon 18 (icons\vol_internal_apfs.icns) not found (path: EFI\CLOVER\themes\Minimalism)
2:447  0:113  - [10]: 'Recovery', hidden
2:447  0:000  - [11]: 'VM'

 

Thanks!

Share this post


Link to post
Share on other sites
Just now, ellaosx said:

Juat set it to LastBootedVolume

 

Unfortunately, I can't since I am using EMUVariableUEFI since my mobo doesn't support native nvram :(

Share this post


Link to post
Share on other sites
16 hours ago, ellaosx said:

install rc script with emuvariable, then LastBootedVolume

 

Oh true, I forgot I could do that. I still wonder what's wrong though, I'm not sure exactly what value should have gone in there to set the macOS volume to be default...

 

Edit: Actually, the last used volume option doesn't seem to stick booting to macOS if change the value to boot into Windows. Ideally I should be able to chose the disk by name or UUID or other value. Any other ideas?

 

Edit 2: It looks like I found the culprit. The boot entry that Clover installed in the NVRAM boot options was pointing to the wrong bootloader. Once I removed that entry, using the full copy-pasted value of HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60) worked for me.

Edited by WanderingAi

Share this post


Link to post
Share on other sites
On 1/8/2019 at 9:06 PM, al6042 said:

Just tried the last official clover release 4842 and got the following errors while trying to check and configure BootChimeCfg.efi on my H170N-Wifi and Prime Z390-A:

1084557407_Clover4842-BootChimeCfg-Error.thumb.jpg.2f40e28621bd940ff562811527013050.jpg

 

Did I miss something?

 

 

I think BootChimeCfg.efi needs to be executable. Which, depending on where did you get it from, it might not be.

 

Personally I couldn't get my system to play the sound.wav file I placed in the theme folder. Not sure why. Still checking a few things.

Edited by arsradu

Share this post


Link to post
Share on other sites

Nope, 

BootChimeCfg.efi was working fine, that's why the last command in the screenshot worked.

The errors with the other options were gone, as soon as an AudioDxe.efi-file was placed in /EFI/CLOVER/driver64UEFI...

Either as manual copy or with clover 4844...

Share this post


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

Nope, 

BootChimeCfg.efi was working fine, that's why the last command in the screenshot worked.

The errors with the other options were gone, as soon as an AudioDxe.efi-file was placed in /EFI/CLOVER/driver64UEFI...

Either as manual copy or with clover 4844...

 

You're correct. After further investigation, it looks like I managed to reproduce the errors you were having. So yeah, it wasn't related to being executable or not. Actually, I think they're made executable anyway, when you drop them in the tools folder. Could be wrong thought. In my case, it was the "sound.wav" file missing from the theme's folder.

 

Still trying to get it to work... So far I managed to set it up... But still no sound on startup. I'm sure there's probably a mistake on my side somewhere.

 

EDIT: if you have more than one SSD/HDD with Clover on it, make sure you set the chime on the correct one.

 

EDIT 2: ok, so now I'm exactly where you are. Managed to set it up for boot (it was a total pain in the rear to find the correct boot EFI partition to load from Shell - for some reason, in my case it was FS11...) and tested it, working fine in Shell, but no sound on boot.

 

My guess is that maybe the sound output device is not selected correctly....? I don't know. What I do know, is that, Clover 4851 has an interface for testing and configuring the boot sound, but it always selects Device Output #1 for some reason...even after I selected Device #8, aaaand...pressing F7 to test that device will freeze the entire UI.

 

screenshot2.thumb.png.528c8b384dbd047e5e4b722f66d49c55.png

 

In my case, I set in the Shell the output device to be the one selected below (nr 8 in the list) but every time I enter here, it shows the first option. My guess is that the output device might haven't been saved. That's why it doesn't make any sound on boot.

 

Also, as I said, pressing F7 here will freeze the interface without making any sound.

 

screenshot3.thumb.png.c76faa99e3cb8460c679310c76e5f72a.png

 

Interestingly enough, it seems to have remembered the correct volume setting (60%). But not the output device.

Edited by arsradu

Share this post


Link to post
Share on other sites
10 hours ago, Slice said:

Correct to


extern UINT8 EmbeddedSound[];

Thats the first thing I tried throws up another error 

/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c: In function 'StartupSoundPlay':
/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c:81:14: error: assignment to 'UINT8 *' {aka 'unsigned char *'} from 'UINT8' {aka 'unsigned char'} makes pointer from integer without a cast [-Werror=int-conversion]
     FileData = EmbeddedSound;
              ^
[CC] ntfscomp
cc1: all warnings being treated as errors
make: *** [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit/OUTPUT/Platform/StartupSound.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
	/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/refit.inf [X64, GCC53, RELEASE]

- Failed -
Build end time: 05:28:45, Jan.19 2019
Build total time: 00:00:41


o_Ops, ./ebuild.sh exited with error(s), aborting..

 

Share this post


Link to post
Share on other sites
14 hours ago, Dr. Hurt said:

 

The boot chime works perfectly using AudioDXE.efi and BootChimeDXE.efi in the drivers64 folder. Those (and only those) two drivers are enough to get the chime going when the macOS boot entry is selected in Clover.

 

The only annoyance for me is that Clover takes 3 extra seconds to start. Hopefully that will be slightly optimized in the future.

 

PS. My laptop does have UEFI but its disabled. I'm using legacy boot.

 

That is exactly where I had those two files. As I said, I got chime to work in Clover Shell, but it wouldn’t play on regular boot.

 

I am also confused, where do I acquire those files? There seems to be some confusion about where to obtain those files.

Edited by pkdesign

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 JhonneR
      Good morning, everyone, I'm sorry if I was wrong in choosing the topic but I need help.
      I have found it extremely difficult to mount a Hackintosh in my acer.
      Setup;
      I5 2430m 2.4 6GB RAM
      Mobo P5we0 - Intel intel Graphics 3000
      At the moment I have not found out what my audio codecs are.
      but I'll leave the link on the motherboard.
      however, my real problem is several.
      I have already used the itakos image, I have already used several images that could be installed normally and that after installing the image I do not have internet via cable or wireless.
      And another, I already looked in other forums and I know that I will be called a donkey in the logical question but I have not been able to install the [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] or clover to start from the Hard Disk, so I do not know what to do.At the moment I still do not know if there has already been someone who has already installed the High Sierra or just the Sierra in this notebook model and obtained permanent success.
      If anyone can help me, I'll be grateful.
      Installations without success, but with the system already installed in ACER;
      SIERRA
      HIGH SIERRA
      MOJAVE
      All with the same symptom. Starting only by the bootable USB stick and without internet connection via cable and wireless.
      Appreciate ! Acer 5750 Official Page
    • By Slice
      Since rev 4844 Vector Themes are supported and there are ready-to-use Clovy by Clovy, cesium by Slice and BGM_SVG by Blackosx.
      You may see it's structure to create own theme
      -------------------------------------------------------------------------------------------------------------------------------------------------------
       
       
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
      Pictures from Badruzeus
      https://www.insanelymac.com/forum/applications/core/interface/file/attachment.php?id=301597
    • 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) 
                               : 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
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip





       

×