Jump to content
ErmaC

Clover Problems and Solutions

2,874 posts in this topic

Recommended Posts

Please be advised that this is not a discussion topic.

 



This topic is a "direct" line of communication between the Developers of Clover (Clover Team).
Unless a Developer/Coder asks for more information, all the critical information of a post should be contained in the subject and first post.
Every post will be responded to in some fashion before being locked.

 

 

 


 


Invalid Posts
Since we are strictly interested in issue reports on this topic, the following post/reply are likely to be deleted immediately:
1. Discussion topic aka OFF-TOPIC (What do you all think?)
2. Invalid issue reports
3. Feedback / Suggestion threads.
4. Posts requesting information about the bootloader.
5. Posts made on other forums (Don't spam.)
6. "Accomplishment" threads, threads to advertise screenshots unrelated to bug reports.
7. Posts requesting status updates on existing issues.

 

 

Share this post


Link to post
Share on other sites
Advertisement

Looks like config.plist/SystemParameters/InjectKexts=Detect is broken.

 

Details:

- config.plist/SystemParameters/InjectKexts=Detect

- FakeSMC.kext installed to /S/L/E

- pressing spacebar on my Yosemite partition shows option for "without kexts"... should be showing option for "with kexts"

- booting normally will inject kexts from Clover/kexts (in Clover bootlog)

- booting "without kexts" works... as FakeSMC.kext *is* installed in /S/L/E and is in the cache

- setting KernelAndKextPatches/Debug=true reveals that Clover is finding FakeSMC present in the cache

 

This used to work, but I'm not sure how long it is broken.

 

No custom entries involved here, although it can be fixed with them (eg. set InjectKexts=false for system partition, true for Recovery)

 

Clover r3206 UEFI built from source.

Share this post


Link to post
Share on other sites

...

if you have FakeSMC in S/L/E you have to have kext-dev-mode=1 in your config.plist arguments, but my main question is why use S/L/E for any kext when you can have Clover inject itself

Share this post


Link to post
Share on other sites

if you have FakeSMC in S/L/E you have to have kext-dev-mode=1 in your config.plist arguments, but my main question is why use S/L/E for any kext when you can have Clover inject itself

I have kext-dev-mode=1 and I'm well aware of its purpose.

 

My bug report has nothing to do with kext-dev-mode=1. It has to do with the fact that InjectKexts=Detect is broken.

 

Kext injection should be used only when necessary (installer/recovery). So... I install everything to /S/L/E where it can go to kernel cache. Note also there are are many kexts which do not work when injected.

Share this post


Link to post
Share on other sites

Looks like config.plist/SystemParameters/InjectKexts=Detect is broken.

 

Details:

...

 

 

Do you maybe remember which was the last build you tried that still worked? Would make it easier to track what has changed since then.

Share this post


Link to post
Share on other sites

Do you maybe remember which was the last build you tried that still worked? Would make it easier to track what has changed since then.

Unfortunately not. I could go back and see if I can find one...

 

But I've been using custom entries with InjectKexts explicitly set (true/false) so I didn't notice the problem until troubleshooting a machine not my own.

 

I went back to as far as r2812 and it is still broken there.

 

I was reviewing the code and I can see where it clears the flag:

VOID CheckForFakeSMC(CHAR8 *InfoPlist, LOADER_ENTRY *Entry)
{
  if (OSFLAG_ISSET(Entry->Flags, OSFLAG_CHECKFAKESMC) &&
      OSFLAG_ISSET(Entry->Flags, OSFLAG_WITHKEXTS)) {
    if (AsciiStrStr(InfoPlist, "<string>org.netkas.driver.FakeSMC</string>") != NULL
        || AsciiStrStr(InfoPlist, "<string>org.netkas.FakeSMC</string>") != NULL)
    {
      Entry->Flags = OSFLAG_UNSET(Entry->Flags, OSFLAG_WITHKEXTS);
      if (Entry->KernelAndKextPatches->KPDebug) {
        DBG_RT(Entry, "\nFakeSMC found\n");
        gBS->Stall(5000000);
      }
    }
  }
}
The "FakeSMC found" trace... I am seeing that, so we know this code is executing.

 

I also see this executed (I see the 'disabled because... Detect' trace):

    //
    // Kext add
    //
    if (Entry != 0 && OSFLAG_ISSET(Entry->Flags, OSFLAG_CHECKFAKESMC) && OSFLAG_ISUNSET(Entry->Flags, OSFLAG_WITHKEXTS)) {
        // disable kext injection if FakeSMC is already present
        Entry->Flags = OSFLAG_UNSET(Entry->Flags, OSFLAG_WITHKEXTS);
        if (Entry->KernelAndKextPatches->KPDebug) {
            DBG_RT(Entry, "\nInjectKexts: disabled because FakeSMC is already present and InjectKexts option set to Detect\n");
            gBS->Stall(500000);
        }
    }
Never mind that the line 'Entry->Flags = OSFLAG_UNSET(Entry->Flags, OSFLAG_WITHKEXTS);' is not needed since we just checked 'OSFLAG_ISUNSET(Entry->Flags, OSFLAG_WITHKEXTS)' in the conditional (eg. the flag is already cleared).

 

The mystery is why when we reach LoadKexts, the flag is set:

EFI_STATUS LoadKexts(IN LOADER_ENTRY *Entry)
{
...
	if ((Entry == 0) || OSFLAG_ISUNSET(Entry->Flags, OSFLAG_WITHKEXTS)) {
		return EFI_NOT_STARTED;
	}
There is some code that duplicates the "main" entry to a subentry. Each of these subentries have their own "Flags", and from what I can tell these subentries will not be modified by this code, so perhaps Clover is actually booting from the subentry, not the main entry?

 

Note (loader.c):

  // default entry
  SubEntry = DuplicateLoaderEntry(Entry);
  if (SubEntry) {
    SubEntry->me.Title = (Entry->LoaderType == OSTYPE_OSX ||
                          Entry->LoaderType == OSTYPE_OSX_INSTALLER ||
                          Entry->LoaderType == OSTYPE_RECOVERY) ?
    L"Boot Mac OS X" : PoolPrint(L"Run %s", FileName);
    AddMenuEntry(SubScreen, (REFIT_MENU_ENTRY *)SubEntry);
  }
Edit: Debugging further. LoadKexts is called before CheckForFakeSMC is called...

 

No idea if there is a difference between "loading kexts" and "injecting kexts". Perhaps in the case of "Detect" kexts are loaded but never injected. The bootlog looks the same in either case:

 

InjectKexts=Detect (FakeSMC in cache)

5:149  0:000  FSInjection: using kexts path: 'EFI\CLOVER\kexts\10.10'FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: B6B2598
5:149  0:000  
5:151  0:001  MSR 0x1B0   set to        00000000
15:152  10:001  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.10
15:155  0:002    Extra kext: EFI\CLOVER\kexts\10.10\AppleIntelE1000e.kext
15:160  0:005    Extra kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext
15:165  0:004      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\ACPISensors.kext
15:168  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\CPUSensors.kext
15:172  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\GPUSensors.kext
15:175  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\LPCSensors.kext
15:183  0:007    Extra kext: EFI\CLOVER\kexts\10.10\GenericUSBXHCI.kext
15:187  0:004  Removed efi-boot-device-data variable: Not Found
15:187  0:000  Custom boot is disabled
15:187  0:000  Closing log
InjectKexts=Yes

6:370  0:000  FSInjection: using kexts path: 'EFI\CLOVER\kexts\10.10'FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: B6B2598
6:371  0:000  
6:373  0:001  MSR 0x1B0   set to        00000000
16:374  10:001  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.10
16:376  0:002    Extra kext: EFI\CLOVER\kexts\10.10\AppleIntelE1000e.kext
16:381  0:004    Extra kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext
16:386  0:004      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\ACPISensors.kext
16:389  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\CPUSensors.kext
16:392  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\GPUSensors.kext
16:396  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext\Contents\PlugIns\LPCSensors.kext
16:404  0:007    Extra kext: EFI\CLOVER\kexts\10.10\GenericUSBXHCI.kext
16:408  0:004  Removed efi-boot-device-data variable: Not Found
16:408  0:000  Custom boot is disabled
16:408  0:000  Closing log
InjectKexts=No

5:191  0:000  FSInjection: skipping kext injection (not requested)FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: B6B2598
5:192  0:000  
5:193  0:001  MSR 0x1B0   set to        00000000
15:195  10:001  Removed efi-boot-device-data variable: Not Found
15:195  0:000  Custom boot is disabled
15:195  0:000  Closing log
Expect: Bootlog with InjectKexts=Detect (and FakeSMC in cache) would look like InjectKexts=No.

Share this post


Link to post
Share on other sites

Never saw this thread before, but since I have a bug report I'll just re-report it here.

 

Theme=embedded + Timeout=0 == autoboot breaks (default entry highlighted but I need to press enter to boot)

TextOnly=True + Timeout=0 == same

 

Theme=embedded + Timeout=5 == WORKS

Theme=iClover + Timeout=0 == WORKS

 

 

0:100  0:100  MemLog inited, TSC freq: 2294785194
0:100  0:000  LegacyRegion2: Chipset/proc: 0x01048086
0:100  0:000   Next Generation Core processors (PAM 0x80-0x86)
0:100  0:000   Test PAM1=(0x41=90, 0x5a=00, 0x81=11, 0x91=00) at chipset 01048086
0:100  0:000  , Install = Success
0:114  0:014  VGA Pci.Hdr.Command=6 - not enabled
0:114  0:000  BiosVideoDriverBindingStart!
0:114  0:000  BiosVideoCheckForVbe
0:114  0:000  EdidOverride not found
0:127  0:012   Edid1+
0:127  0:000   found Detail Timing 1366x768
0:127  0:000   found Detail Timing 1366x768
0:127  0:000  timing string after 0xFE:4Y4GM?156AT
 
0:139  0:012   Edid0+
0:139  0:000   found Detail Timing 1366x768
0:139  0:000  ... already present
0:139  0:000   found Detail Timing 1366x768
0:139  0:000  ... already present
0:139  0:000  timing string after 0xFE:4Y4GM?156AT
 
0:140  0:000     0 1024x768 attr=9B - ok, edid-, 1024x768, working, highest, pref=0
0:140  0:000     1 640x480 attr=9B - ok, edid-, 640x480, working
0:140  0:000     2 800x600 attr=9B - ok, edid-, 800x600, working
0:140  0:000     3 1366x768 attr=9B - ok, edid+, working, highest, pref=3
0:140  0:000  BV new mode: 3 1366x768
0:277  0:137   SetMode pref 3 (3) = Success
0:278  0:000  VGA Pci.Hdr.Command=6 - not enabled
0:363  0:084  VGA Pci.Hdr.Command=6 - not enabled
0:368  0:005  VGA Pci.Hdr.Command=6 - not enabled
0:369  0:001  Found supported controller for BiosBlockIO class=010601
0:369  0:000  Int13Extensions: INT 13 41 DL=80 : CF=0 BX=AA55 CX=0001
0:369  0:000  GetDriveParameters: INT 13 48 DL=80 : CF=0 AH=00
0:369  0:000  BlockSize = 512  LastBlock = 976773167
0:372  0:002  Int13Extensions: INT 13 41 DL=F2 : CF=0 BX=AA55 CX=0005
0:372  0:000  GetDriveParameters: INT 13 48 DL=F2 : CF=0 AH=00
0:372  0:000  BlockSize = 2048  LastBlock = -1
0:600  0:228  VGA Pci.Hdr.Command=6 - not enabled
0:955  0:354  
0:955  0:000  Now is 14.5.2015,  15:36:27 (GMT+2047)
0:955  0:000  Starting Clover rev 3202 on CLOVER EFI
0:955  0:000  SelfDevicePath=PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(1,GPT,8A941F7C-3F7C-48D0-AD86-1B8BA302E4E4,0x28,0x64000) @1F43BC98
0:955  0:000  SelfDirPath = \EFI\CLOVER
0:955  0:000  Total Memory Slots Count = 2
0:955  0:000  Type 17 Index = 0
0:955  0:000  Table has error information, checking
0:955  0:000  Ignoring insane frequency value 0MHz
0:955  0:000  SmbiosTable.Type17->Speed = 0MHz
0:955  0:000  SmbiosTable.Type17->Size = 0MB
0:955  0:000  SmbiosTable.Type17->Bank/Device = BANK 0 DIMM_A
0:956  0:000  Type 17 Index = 1
0:956  0:000  Table has error information, checking
0:956  0:000  SmbiosTable.Type17->Speed = 1333MHz
0:956  0:000  SmbiosTable.Type17->Size = 4096MB
0:956  0:000  SmbiosTable.Type17->Bank/Device = BANK 2 DIMM_B
0:956  0:000  Boot status=0
0:956  0:000  Clover revision: 3202  running on Inspiron N5110
0:956  0:000  ... with board 0FXK2Y
0:956  0:000  CPU Vendor = 756E6547 Model=206A7
0:956  0:000  The CPU supported turbo
0:956  0:000  BrandString = Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz
0:956  0:000  MSR 0xE2 before patch 1E000404
0:956  0:000  MSR 0xE4              00020414
0:956  0:000  MSR 0xCE              00000800_60011700
0:956  0:000  non-usable FLEX_RATIO = 10000
0:956  0:000  corrected FLEX_RATIO = 0
0:956  0:000  MSR 0x1B0             00000000
0:956  0:000  FSBFrequency=100MHz DMIvalue=100000kHz
0:956  0:000  Corrected FSBFrequency=100MHz
0:956  0:000  Vendor/Model/Stepping: 0x756E6547/0x2A/0x7
0:956  0:000  Family/ExtFamily: 0x6/0x0
0:956  0:000  MaxDiv/MinDiv: 23.0/8
0:956  0:000  Turbo: 27/27/27/29
0:956  0:000  Features: 0xBFEBFBFF
0:956  0:000  Threads: 4
0:956  0:000  Cores: 2
0:956  0:000  FSB: 100 MHz
0:956  0:000  CPU: 2300 MHz
0:956  0:000  TSC: 2300 MHz
0:956  0:000  PIS: 400 MHz
0:956  0:000  PCI (00|00:00.00) : 8086 0104 class=060000
0:956  0:000  PCI (00|00:01.00) : 8086 0101 class=060400
0:956  0:000  PCI (00|01:00.00) : 10DE 0DF5 class=030000
0:956  0:000  Found NVidia model=Dell GeForce GT 525M
0:956  0:000  PCI (00|01:00.01) : 10DE 0BEA class=040300
0:956  0:000  PCI (00|00:02.00) : 8086 0116 class=030000
0:956  0:000  Found GFX model=Intel HD Graphics 3000
0:956  0:000  PCI (00|00:16.00) : 8086 1C3A class=078000
0:956  0:000  PCI (00|00:1A.00) : 8086 1C2D class=0C0320
0:956  0:000  PCI (00|00:1B.00) : 8086 1C20 class=040300
0:956  0:000  PCI (00|00:1C.00) : 8086 1C10 class=060400
0:956  0:000  PCI (00|00:1C.01) : 8086 1C12 class=060400
0:956  0:000  PCI (00|05:00.00) : 10EC 8136 class=020000
0:956  0:000  LAN 0, Vendor=10EC, MMIO=D000
0:956  0:000  PCI (00|00:1C.03) : 8086 1C16 class=060400
0:956  0:000  PCI (00|09:00.00) : 168C 002B class=028000
0:956  0:000  PCI (00|00:1C.04) : 8086 1C18 class=060400
0:956  0:000  PCI (00|0B:00.00) : 1033 0194 class=0C0330
0:956  0:000  PCI (00|00:1C.07) : 8086 1C1E class=060400
0:956  0:000  PCI (00|00:1D.00) : 8086 1C26 class=0C0320
0:956  0:000  PCI (00|00:1F.00) : 8086 1C4B class=060100
0:956  0:000  PCI (00|00:1F.02) : 8086 1C03 class=010601
0:956  0:000  PCI (00|00:1F.03) : 8086 1C22 class=0C0500
0:956  0:000  Clover load options size = 0 bytes
0:978  0:021  Using OEM config.plist at path: EFI\CLOVER\config.plist
0:978  0:000  EFI\CLOVER\config.plist loaded: Success
0:986  0:007  Found theme directory: random
0:991  0:005  Loading early settings
0:991  0:000  timeout set to 0
0:991  0:000  Custom boot CUSTOM_BOOT_DISABLED (0x0)
0:991  0:000  Default theme: embedded
0:991  0:000  LoadDrivers() start
0:991  0:000  Loading FSInject-64.efi  status=Success
1:020  0:028  Loading HFSPlus.efi  status=Success
1:020  0:000   - driver needs connecting
1:020  0:000  1 drivers needs connecting ...
1:020  0:000  PlatformDriverOverrideProtocol->GetDriver overriden
1:020  0:000  HFS+ driver loaded 
1:026  0:006  VGA Pci.Hdr.Command=6 - not enabled
1:186  0:159  LoadDrivers() end
1:186  0:000  Console modes reported: 4, available modes:
1:186  0:000    Mode 1: 80x25
1:186  0:000    Mode 3: 100x31
1:186  0:000    Mode 4: 170x40 (current mode)
1:186  0:000  SetScreenResolution: 1366x768 - already set
1:186  0:000  reinit: self device path=PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(1,GPT,8A941F7C-3F7C-48D0-AD86-1B8BA302E4E4,0x28,0x64000)
1:186  0:000   get legacy LAN MAC, 1 card found
1:186  0:000  Legacy MAC address of LAN #0= 18:03:73:53:27:20:
1:186  0:000  ScanSPD() start
1:186  0:000  SMBus CmdReg: 0x3
1:186  0:000  Scanning SMBus [8086:1C22], mmio: 0xF7B05004, ioport: 0xF040, hostc: 0x1
1:186  0:000  Slots to scan [8]...
1:213  0:026  SPD[2]: Type 11 @0x52 
1:222  0:009  Not using XMP because it is not present
1:222  0:000  DDR speed 1333MHz 
1:222  0:000  Slot: 2 Type 24 4096MB 1333MHz Vendor=Hynix Semiconductor PartNo=HMT351S6BFR8C-H9N0 SerialNo=0508040A0803030A 
1:252  0:030  ScanSPD() end
1:262  0:009  Get Acpi Tables List from RSDT:
1:262  0:000   Found table: FACP  WN09 len=132
1:262  0:000   Found table: APIC  WN09 len=114
1:262  0:000   Found table: MCFG  WN09 len=60
1:262  0:000   Found table: SSDT  PtidDevc len=1200
1:262  0:000   Found table: HPET  WN09 len=56
1:262  0:000   Found table: SSDT  Cpu0Ist len=1920
1:262  0:000   Found table: SSDT  CpuPm len=2454
1:262  0:000   Found table: SSDT  SgTabl len=3456
1:262  0:000   Found table: SSDT  OptTabl len=5353
1:262  0:000   Found table: OSFR  M08     len=134
1:262  0:000  Calibrated TSC frequency =2294785194 =2294MHz
1:262  0:000  Loading main settings
1:262  0:000  Dropping 2 tables
1:262  0:000  Drop table 0 signature="SSDT" (54445353) table-id="CpuPm" (0000006D50757043)
1:262  0:000  set table: 54445353,       6D50757043 to drop:  true
1:262  0:000  
1:262  0:000  Drop table 1 signature="SSDT" (54445353) table-id="Cpu0Ist" (0074734930757043)
1:262  0:000  set table: 54445353,   74734930757043 to drop:  true
1:262  0:000  
1:262  0:000  Config set Fixes will override FixMask mask!
1:262  0:000     final mask=00000000
1:262  0:000  Config set EnableC7: +
1:262  0:000  Config set EnableC6: +
1:262  0:000  Config set EnableC4: +
1:262  0:000  Config set EnableC2: +
1:290  0:028  found 8 volumes with blockIO
1:290  0:000   0. Volume:
1:290  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)
1:301  0:011    Result of bootcode detection: bootable unknown (legacy)
1:301  0:000   1. Volume:
1:301  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,F2)
1:301  0:000    found optical drive
1:301  0:000  Detected name 
1:301  0:000    Result of bootcode detection: bootable unknown (legacy)
1:301  0:000   2. Volume:
1:301  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(1,GPT,8A941F7C-3F7C-48D0-AD86-1B8BA302E4E4,0x28,0x64000)
1:302  0:000    Result of bootcode detection: bootable Clover (clover)
1:302  0:000    This is SelfVolume !!
1:302  0:000   3. Volume:
1:302  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(2,GPT,A2B67513-8F9B-4D6D-A4B1-C232D2E3D608,0x64028,0x403B5B0)
1:302  0:000   4. Volume:
1:302  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(3,GPT,39FE376A-5300-40AF-AA42-E152EFDD7D0D,0x409F5D8,0x135F20)
1:303  0:000   5. Volume:
1:303  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(4,GPT,2F3A0E7E-4AC9-4C0C-994A-BC9D60679C92,0x41D54F8,0x30E43308)
1:303  0:000    Result of bootcode detection: bootable Windows (vista,win)
1:303  0:000   6. Volume:
1:303  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(5,GPT,6D359B48-3A3A-4857-AC96-08266B07FE5D,0x35058800,0x40000)
1:303  0:000   7. Volume:
1:303  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(6,GPT,2ABF778B-330C-4410-905F-6C9CBD223163,0x35098800,0x52B2800)
1:304  0:000    Result of bootcode detection: bootable Windows (vista,win)
1:304  0:000  PutNvramPlistToRtVars: nvram.plist not found
1:304  0:000   using embedded theme
1:304  0:000  Choosing theme <null string>
1:304  0:000  Custom entries start
1:304  0:000  Custom entries finish
1:304  0:000  Scanning loaders...
1:304  0:000   0: 'Whole Disc Boot' no file system
1:304  0:000   1: '' no file system
1:304  0:000   2: 'EFI'
1:354  0:050      AddLoaderEntry for Volume Name=EFI
1:382  0:027   3: 'Macintosh'
1:408  0:025      AddLoaderEntry for Volume Name=Macintosh
1:440  0:032      Check if volume Is Hibernated:
1:440  0:000      Check sleep image 'by signature':
1:481  0:041      read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success
1:481  0:000      using default sleep image name = \private\var\vm\sleepimage
1:496  0:014      Reading first 512 bytes of sleepimage ...
1:502  0:006   OurBlockIoRead: Lba=13CD940, Offset=279B28000 (BlockSize=512)
1:502  0:000   sig lion: 7A7A7A7A
1:502  0:000   sig snow: 0
1:502  0:000   no valid sleep image offset was found
1:502  0:000      Reading completed -> Success
1:502  0:000       sleepimage offset could not be acquired
1:502  0:000       hibernated: no - sign
1:506  0:003   4: 'Recovery HD'
1:520  0:014      AddLoaderEntry for Volume Name=Recovery HD
1:536  0:015   5: 'Legacy HD4' no file system
1:536  0:000   6: 'Legacy HD5' no file system
1:536  0:000   7: 'Legacy HD6' no file system
1:536  0:000  Custom legacy start
1:536  0:000  Custom legacy end
1:536  0:000  Custom tool start
1:536  0:000  Custom tool end
1:536  0:000  GetEfiBootDeviceFromNvram: efi-boot-device-data not found
1:536  0:000  EfiBootVolume not found
1:536  0:000   found entry 1. 'Boot Mac OS X from Macintosh', Volume 'Macintosh', DevicePath 'PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(2,GPT,A2B67513-8F9B-4D6D-A4B1-C232D2E3D608,0x64028,0x403B5B0)\System\Library\CoreServices\boot.efi'
1:536  0:000  DefaultIndex=1 and MainMenu.EntryCount=7
1:639  0:102  GUI ready
3:703  2:063  BootOption of the entry is empty
3:703  0:000  StartLoader() start
3:703  0:000  Finally: Bus=99773kHz CPU=2294MHz
3:703  0:000  Kernel and Kext Patches at 1F7D82F0:
3:703  0:000   Allowed: y
3:703  0:000   Debug: n
3:703  0:000   KernelCpu: n
3:703  0:000   Lapic: n
3:703  0:000   Haswell-E: n
3:703  0:000   AICPUPM: n
3:703  0:000   AppleRTC: y
3:703  0:000   KernelPm: n
3:703  0:000   FakeCPUID: 0x0
3:703  0:000   ATIController: null
3:703  0:000   ATIDataLength: 0
3:703  0:000   0 Kexts to load
3:703  0:000   0 Kexts to patch
3:703  0:000  Loading boot.efi  status=Success
3:872  0:169  GetOSVersion: : 10.10.3
3:872  0:000  insert table 9 for dev 0:0
3:872  0:000  insert table 9 for dev 0:0
3:872  0:000  insert table 9 for dev 0:0
3:872  0:000  Trusting SMBIOS...
3:872  0:000  Detected alternating SMBIOS channel banks
3:872  0:000  Channels: 1
3:872  0:000  Interleave: 0 1 2 3 4 5 6 7
3:872  0:000  SMBIOS Type 17 Index = 0 => 0 0:
3:872  0:000  BANK0 DIMM0 EMPTY
3:872  0:000   partNum=HMT351S6BFR8C-H9  
3:872  0:000  SMBIOS Type 17 Index = 1 => 1 1:
3:872  0:000  BANK0 DIMM1 1333MHz 4096MB
3:872  0:000  mTotalSystemMemory = 4096
3:872  0:000  NumberOfMemoryDevices = 2
3:872  0:000  Type20[0]->End = 0x3FFFFF, Type17[1] = 0x1000
3:872  0:000  Table 131 is present, CPUType=31
3:872  0:000  Change to: 603
3:872  0:000  RSDT 0xCAFAD028
3:872  0:000  FADT from RSDT: 0xCAFAD0F8
3:872  0:000  XSDT 0xCAFAD078
3:872  0:000  FADT from XSDT: 0xCAFB6CA8
3:872  0:000  Xsdt reallocation done
3:872  0:000  old FADT length=F4
3:872  0:000  Found OperationRegion(DEBU, SystemMemory, CAFE7F98, ...)
3:872  0:000  Found OperationRegion(GNVS, SystemMemory, CAFDCE18, ...)
3:873  0:000  Found OperationRegion(EXBU, SystemMemory, CAFE5018, ...)
3:873  0:000  Found OperationRegion(MCHT, SystemMemory, FED10000, ...)
3:873  0:000  Found OperationRegion(RCRB, SystemMemory, FED1C000, ...)
3:873  0:000  Found OperationRegion(CPSB, SystemMemory, CAFF4F98, ...)
3:873  0:000  Found OperationRegion(IGDM, SystemMemory, 0, ...)
3:873  0:000  Found OperationRegion(MBOX, SystemMemory, FE800000, ...)
3:873  0:000  Found OperationRegion(MMBX, SystemMemory, FE800000, ...)
3:889  0:016  DSDT found in Clover volume OEM folder: EFI\CLOVER\ACPI\patched\DSDT.aml
3:892  0:003  Apply DsdtFixMask=0x00000000 old way
3:892  0:000     drop _DSM mask=0xFFFF
3:892  0:000  ========= Auto patch DSDT Starting ========
3:892  0:000  VideoCard devID=0xDF510DE
3:892  0:000  DisplayADR1[0] = 0x10000, DisplayADR2[0] = 0x0
3:892  0:000  VideoCard devID=0x1168086
3:892  0:000  DisplayADR1[1] = 0x20000, DisplayADR2[1] = 0xFFFE
3:892  0:000  USBADR[0] = 0x1A0000 and PCIe = 0xFFFE
3:893  0:000  Found Airport Atheros at 0x1C0003, 0x0, DeviceID=0x002B
3:893  0:000  USBADR[1] = 0x1C0004 and PCIe = 0x0
3:893  0:000  USBADR[2] = 0x1D0000 and PCIe = 0xFFFE
3:893  0:000  first CPU found at 604A offset 604D
3:893  0:000  score candidate at 6046
3:893  0:000  score inserted in acpi_cpu_score _PR_
3:893  0:000  Found ACPI CPU: CPU0 And CPU1 And CPU2 And CPU3 And CPU4 And CPU5 And CPU6 And CPU7 
  within the score: _PR_
3:893  0:000  Found PCIROOTUID = 0
3:893  0:000  ========= Auto patch DSDT Finished ========
3:893  0:000  Drop tables from Xsdt, SIGN=SSDT TableID=CpuPm Length=2454
3:893  0:000   Xsdt has tables count=10 
3:893  0:000   Table: SSDT  CpuPm  2454 dropped
3:893  0:000  corrected XSDT length=108
3:893  0:000  Drop tables from Xsdt, SIGN=SSDT TableID=Cpu0Ist Length=1920
3:893  0:000   Xsdt has tables count=9 
3:893  0:000   Table: SSDT  Cpu0Ist  1920 dropped
3:893  0:000  corrected XSDT length=100
3:893  0:000  Patch table: SSDT  PtidDevc
3:893  0:000   SSDT len = 0x4B0
3:893  0:000  Patch table: SSDT  SgTabl
3:893  0:000   SSDT len = 0xD80
3:893  0:000  Patch table: SSDT  OptTabl
3:893  0:000   SSDT len = 0x14E9
3:893  0:000  Drop tables from Xsdt, SIGN=XXXX TableID= Length=0
3:893  0:000   Xsdt has tables count=8 
3:893  0:000  corrected XSDT length=100
3:893  0:000   CPUBase=0 and ApicCPUBase=1 ApicCPUNum=4
3:893  0:000  Maximum control=0x17
3:893  0:000  Turbo control=0x1D
3:893  0:000  P-States: min 0x8, max 0x1D
3:893  0:000  SSDT with CPU P-States generated successfully
3:893  0:000  SSDT with CPU C-States generated successfully
3:893  0:000  EdidDiscovered size=128
3:893  0:000  00 | 00 FF FF FF FF FF FF 00 4C A3 41 54 00 00 00 00 
3:893  0:000  16 | 00 14 01 04 90 22 13 78 0A C8 95 9E 57 54 92 26 
3:893  0:000  32 | 0F 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 
3:893  0:000  48 | 01 01 01 01 01 01 F5 1D 56 FC 50 00 16 30 30 20 
3:893  0:000  64 | 25 00 58 C2 10 00 00 1A D6 12 56 A0 50 00 16 30 
3:893  0:000  80 | 30 20 25 00 58 C2 10 00 00 1A 00 00 00 FE 00 34 
3:893  0:000  96 | 59 34 47 4D 80 31 35 36 41 54 0A 20 00 00 00 00 
3:893  0:000  112 | 00 00 41 01 96 00 00 00 00 01 01 0A 20 20 00 CF 
3:893  0:000  NVidia GFX injection not set
3:893  0:000  Intel GFX injection not set
3:894  0:000  HDA Controller [8086:1C20] :: PcieRoot(0x0)\Pci(0x1B,0x0) => detected codec: 111D:76D1
3:894  0:000  LAN Controller [10EC:8136] :: PcieRoot(0x0)\Pci(0x1C,0x1)\Pci(0x0,0x0)
3:894  0:000  stringlength = 556
3:894  0:000  CurrentMode: Width=1366 Height=768
3:894  0:000  FSInjection: using kexts path: 'EFI\CLOVER\kexts\10.10'FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 1F43BA98
3:896  0:002  
3:897  0:000  MSR 0x1B0   set to        00000000
3:897  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.10
3:912  0:014  Removed efi-boot-device-data variable: Not Found
3:912  0:000  Custom boot is disabled
 
3:912  0:000  Closing log

Share this post


Link to post
Share on other sites

another is F3 at clover menu will not "unhide" Recovery partition if you have it hidden.

Are you sure I am not having that particular problem.

Share this post


Link to post
Share on other sites

3206 Timout  not working anymore today !

i try everything as possible I think?  :moil:

One day long and nothing :wallbash: :wallbash:

Share this post


Link to post
Share on other sites

 

Never saw this thread before, but since I have a bug report I'll just re-report it here.

 

Theme=embedded + Timeout=0 == autoboot breaks (default entry highlighted but I need to press enter to boot)

TextOnly=True + Timeout=0 == same

 

<key>Fast<key>

<true/>

and I have no problems.

Share this post


Link to post
Share on other sites

<key>Fast<key>

<true/>

and I have no problems.

That's a workaround, not a fix!! (Might help narrow down possible causes).

 

Anyway, I can't use this because I need the menu for dual booting.

Share this post


Link to post
Share on other sites

Edit: Debugging further. LoadKexts is called before CheckForFakeSMC is called...

 Thank you for the analysis, it may be really the bug.

Expect: Bootlog with InjectKexts=Detect (and FakeSMC in cache) would look like InjectKexts=No.

Yes, and it is happen for me.

I have InjectKexts=Detect in config.plist

I have FakeSMC in SLE and I see only kernelcache loaded, no additional kexts. While they are present in Clover/..kexts.... folder.I am not using custom entries.

No idea if there is a difference between "loading kexts" and "injecting kexts".

LoadKexts works for kexts forced in config.plist

   // Force kexts to load
   if ((Entry->KernelAndKextPatches != NULL) &&
      (Entry->KernelAndKextPatches->NrForceKexts > 0) &&
      (Entry->KernelAndKextPatches->ForceKexts != NULL)) {

Share this post


Link to post
Share on other sites

...

LoadKexts works for kexts forced in config.plist

   // Force kexts to load
   if ((Entry->KernelAndKextPatches != NULL) &&
      (Entry->KernelAndKextPatches->NrForceKexts > 0) &&
      (Entry->KernelAndKextPatches->ForceKexts != NULL)) {

 

I'll try to look into that... I do not have any ForceKextsToLoad, but maybe something else triggers these settings.

Share this post


Link to post
Share on other sites

Lower case typo for DSDT autopatch.

 

FixBiosDsdt.c at line 2852

aml_add_string_buffer(pack, "Ethernet");
I think need to be in lower case

aml_add_string_buffer(pack, "ethernet");
ErmaC

Share this post


Link to post
Share on other sites

Lower case typo for DSDT autopatch.

 

FixBiosDsdt.c at line 2852

aml_add_string_buffer(pack, "Ethernet");
I think need to be in lower case

aml_add_string_buffer(pack, "ethernet");
ErmaC

 

There are different names.

device_type = "Ethernet"

name =  "ethernet"

But I see somehow strange that we write 

name = "pci1431,0013" for example.

The difference may occurred from different OSX version or just Apple do this differently on different Macs.

Share this post


Link to post
Share on other sites

There are different names.

device_type = "Ethernet"

name =  "ethernet"

But I see somehow strange that we write 

name = "pci1431,0013" for example.

The difference may occurred from different OSX version or just Apple do this differently on different Macs.

Yep I'm refear to name = ethernet

From a real Mac (MacMini)

I see only this...

 

GIGE.png

I'm unable to find the upper-case case (Ethernet) with this original configuration...

 

ErmaC

Share this post


Link to post
Share on other sites

See /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleBCM5701Ethernet.kext/Contents/Info.plist

Screen Shot 2015-05-19 at 7.47.57.png

For the kext to load its name must be "pci14e4,1684" but not 'ethernet" as Apple did.

There is a question. How can Apple did this? I see other way for kext matching.


MacPro5,1

Screen Shot 2015-05-19 at 7.55.57.png

Share this post


Link to post
Share on other sites

There are different names.

device_type = "Ethernet"

name =  "ethernet"

But I see somehow strange that we write 

name = "pci1431,0013" for example.

The difference may occurred from different OSX version or just Apple do this differently on different Macs.

Thx Slice.

So... on the other hand the typo is here...

device_inject.c

line: 383

  devprop_add_value(device, "device_type", (UINT8*)"ethernet", 9);

ErmaC

Share this post


Link to post
Share on other sites

not building
Clover Update Detected !

******** Clover Package STATS **********

*       local  revision at 3217        *

*       remote revision at 3218        *

*       Package Built   =  No          *

****************************************

 

Getting SVN Source, Hang ten…

    Checked edk2 SVN, 'No updates were found...'

 

    Checked, Updates found...

    Auto Updating Clover From 3217 to 3218 ...

 

Local file(s) needs update:

CloverPackage/package/po/clover.pot

CloverPackage/package/po/de.po

CloverPackage/package/po/en.po

CloverPackage/package/po/es.po

CloverPackage/package/po/fr.po

CloverPackage/package/po/hr.po

CloverPackage/package/po/id.po

CloverPackage/package/po/it.po

CloverPackage/package/po/ja.po

CloverPackage/package/po/ko.po

CloverPackage/package/po/lv.po

CloverPackage/package/po/nl.po

CloverPackage/package/po/pl.po

CloverPackage/package/po/pt-BR.po

CloverPackage/package/po/pt.po

CloverPackage/package/po/ru.po

CloverPackage/package/po/sv.po

CloverPackage/package/po/tr.po

CloverPackage/package/po/uk.po

CloverPackage/package/po/zh_CN.po

CloverPackage/package/po/zh_TW.po

Not updating local repository ! Press any key to continue…

    

    Svn up Clover svn://svn.code.sf.net/p/cloverefiboot/code ERROR!!

Share this post


Link to post
Share on other sites

Year update for Clover pkg.

 

year_00.png

This tiny mod (same I do for Chameleon pkg) autoupdate the "last" year int the credits file with out the need to change it any new year...

 

--> year_autoupdate.txt

 

After apply the mod.

year_01.png

 

Enjoy.

 

ErmaC

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave Beta:  For macOS Mojave Beta, use CMJI.tool on page 4 of thread.
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By fantomas1
      -----------------------------
      Mise à jour 12/07/2018
      -----------------------------
       
      La sortie de macOS 10.14 Beta m'oblige à mettre ce topic à jour. Plus de détails dans ce post.
       

       

       
      -----------------------------
      Mise à jour 09/06/2017
       
      -----------------------------
       
      La sortie de macOS 10.13 Beta m'oblige à mettre ce topic à jour. Plus de détails dans ce post.
       

       
       
       
      -----------------------------
      Mise à jour 15/06/2016
      -----------------------------
       
      Une petite mise à jour du topic pour confirmer le bon fonctionnement du patch à la volé de Clover (r3561) avec macOS Sierra.
       

       
       
       
      -----------------------------
      Mise à jour 24/08/2015
      -----------------------------
       
      ok, très bien,
       
      comme pour la HD6770, la nouvelle méthode du patch à la volé est de nouveau fonctionnel et avec les dernières versions de Clover.
       
      pour ma part, je suis sur El Capitan DB7 et Clover r3259
       

       
       
      par contre, je suis toujours obligé de m’aider de l’astuce avec FakeSMC pour que mes kexts soient toujours chargés, mais au moins cela marche.   
       
       
       
       
      et pour config.plist, cela donne ça :
       

       
       
      ceci est juste un exemple avec ma HD4830, il va de soi que vous devez mettre Device-ID de votre carte graphique !!!
       
       
       
       
       
      Salut à tou(te)s
       
      Comme certain(e)s le savent, les cartes graphiques dites "Exotiques" ne sont pas supportés par le système d'exploitation d'Apple.
      En sus d'ajouter l'identifient de la carte graphique (Device ID) dans l'Info.plist du ou des kexts concernés, il faut aussi interagir sur la partie "binaire" du kext par le biais du "patching".
       
      Dans notre cas, les cartes graphiques exotiques sont les cartes AMD (anciennement ATI) de la série HD 48xx, et plus précisément les HD 4830, HD4850, HD4870x2 et HD4890.*
       
      Donc le but est de faire fonctionner ces cartes graphiques de manière stable et fluide en activant QE_CI, chose nécessaire pour en profiter pleinement du système d'exploitation.
       
      * Juste avant de commencer, vous l'avez peut-être remarqué, la HD4870 n'est pas sur la liste suscitée et pour cause c'est que cette carte graphique est nativement supportée par le système d'exploitation d'Apple. Son Device ID est 0x94401002 que vous pouvez trouvé dans l'Info.plist des kexts concernés et c'est celui-ci que nous allons utiliser afin de le remplacer par le Device ID de notre carte graphique.
       
      ** Ce tuto est fait pour fonctionner sous OS X Mavericks, mais il doit fonctionner aussi avec les autres. La seule chose différente c'est l'adresse binaire à patcher.    
       
       
      Très bien, comme le titre le suggère, nous allons voir comment faire reconnaître ces cartes graphiques sous Clover et obtenir par la même un QE_CI activé et parfaitement fonctionnelle.
       
      Je vais utiliser ma Sapphire HD4830 512 MB GDDR3 PCI-E (comme cobaye    ) pour ce test et qui a pour Device ID 0x944c1002.
       
      Pour que ce test réussisse, nous allons donc utiliser ces 2 kexts, à savoir AMD4800Controller.kext (pour la partie QE) et ATIRadeonX2000.kext (pour la partie CI) et allons ajouter notre Device ID dans l'Info.plist. via le tweak "KernelAndKextPatches"
       
      Donc les valeurs à entrer dans notre config.plist sont celle-ci :
      <key>KernelAndKextPatches</key>     <array>         <dict>             <key>Name</key>             <string>AMD4800Controller</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>     </array> Comme vous pouvez le voir, la clé "InfoPlistPatch" sert à injecter notre Device ID "uniquement" dans Info.plist, sans y toucher à la partie "binaire" de nos kexts. La clé "Find" a pour fonction de trouver le Device ID que l'on veut remplacer par le notre en utilisant la clé "Replace".
       
      Très bien, maintenant comme nous l'avons dit au début de ce tutoriel, ajouter notre Device ID n'est pas suffisant pour faire fonctionner pleinement notre carte graphique, il faut encore interagir sur la partie "binaire" de nos kexts. Dans notre cas, il va falloir agir uniquement sur un kext, çàd sur ATIRadeonX2000.kext et plus particulièrement sur ATIRadeonX2000.kext/Contents/MacOS/ATIRadeonX2000
       
      Et pour cela, nous allons faire comme ceci :
      <key>KextsToPatch</key> <array> <dict>     <key>Name</key>     <string>ATIRadeonX2000</string>     <key>Find</key>     <data>0F8394010000</data>     <key>Replace</key>     <data>909090909090</data> </dict> </array> Là nous pouvons voir que la clé "InfoPlistPatch" n'est pas utilisée et donc ces valeurs n'auront aucun effet sur l'Info.plist mais agiront uniquement au niveau de la partie "binaire". 
       
      Et voici les valeurs en leur forme complète que vous devrez ajouter dans votre config.plist
      <key>KernelAndKextPatches</key>     <array>         <dict>             <key>Name</key>             <string>AMD4800Controller</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>Find</key>             <data>0F8394010000</data>             <key>Replace</key>             <data>909090909090</data>        </dict>     </array> Très bien, maintenant il ne nous reste plus qu'à autoriser l'injection des kexts, sans quoi le patch ne fonctionnera pas. Et nous allons le faire via le tweak "InjectKexts" comme ceci :
      <key>SystemParameters</key> --> clé principale <dict>       <key>InjectSystemID</key>       <true/>       <key>InjectKexts</key> --> sous clé       <string>Yes</string> </dict>  
       
      Si certain(e)s d'entre vous préfèrent utiliser le logiciel "Clover Configurator" pour plus de facilité, voici comment entrer ces valeurs :
       
      Allez sur l'onglet "Kernel And Kext Patches" et faites comme ceci :
       
       
       
      *Ne faites pas attention sur le majuscule/minuscule, cela ne fait aucune différence
       
       
      Et pour injecter les kexts, aller sur l'onglet "System Parameters" et mettez l'option Inject Kexts sur Yes comme ceci :
       

       
       
      Voilà, vous n'avez plus qu'à enregistrer les ajustements, redémarrer votre pc et apprécier le résultat.
       
       
      MAIS ... seulement voilà ... il y a un problème ... 
       
      Quoi ? 
       
      Initialement, les kexts ne sont pas présents dans le kernelcache à cause de "OSBundleRequired=Safe Boot" (ils ne sont pas chargés en local par défaut mais en mode sans échec) et donc le patchage "à la volé" (on the fly) ne fonctionnera pas.
       
      Donc quoi, tout ça pour rien ?
       
      Non, bien-sûr, voici l'astuce pour remédier à cela :
       
      Dans un premier temps, il vous faut booter l'OS sans kernelcache. Si vous utiliser Clover Configurator, il vous suffit juste de cocher l'option "No Caches" dans l'onglet "System and Parameters" ou bien vous le faites directement dans votre config.plist :
      <key>SystemParameters</key> <dict>       <key>InjectSystemID</key>       <true/>       <key>InjectKexts</key>       <string>Yes</string>       <key>NoCaches</key>       <true/> </dict> Ceci aura donc pour effet de bloquer kernelcache et obliger boot.efi de charger le kernel et les kexts séparément. Clover et FSInject vont ensuite intercepter tous les chargements des kexts par boot.efi et changer "OSBundleRequired=Safe Boot" en "OSBundleRequired=Root" à la volé (on the fly) et forceront boot .efi à charger les kexts. Et ensuite dans un second temps, Clover va patcher l'Info.plist de ces deux kexts et la partie binaire de ATIRadeonX2000, kernel va les charger et ils seront rattachés à votre carte graphique.
       
      Une fois ceci fait (donc les kexts utilisés), il vous suffit de faire sudo touch /System/Library/Extensions. Ceci créera un nouveau kernelcache qui cette fois-ci contiendra vos kexts utilisés. Ensuite il ne vous reste plus qu'à redémarrer normalement (en décochant l'option No Caches dans Clover Configurator) et le patch fonctionnera à merveille.
       
       
      Oui, mais ... là aussi ...
       
      Quoi encore ?
       
      Seulement voilà, pour une raison ou une autre, il peut arriver que kernelcache se reconstruit tout seul et le patch "à la volé" ne fonctionne plus.
       
      Alors je fais quoi moi en attendant ?
       
      L'astuce la plus efficace pour le moment est d'injecter les infos de vos kexts à l'intérieur de l'Info.plist de FakeSMC.kext comme des IOKitPersonalities additionnels.
       
      ????Kézako????
       
      Ces infos vous les trouverez dans l'Info.plist de ces 2 kexts, sous IOKitPersonalities. Les voici :
       
      Pour AMD4800Controller.kext
      <key>Controller</key> <dict>         <key>ATY,Cardinal</key>         <dict>                 <key>aty_config</key>                 <dict>                         <key>CFG_NO_PP</key>                         <true/>                 </dict>          </dict>          <key>CFBundleIdentifier</key>          <string>com.apple.kext.AMD4800Controller</string>          <key>IOClass</key>          <string>AMD4800Controller</string>          <key>IOMatchCategory</key>          <string>IOFramebuffer</string>          <key>IOName</key>          <string>AMD4800Controller</string>          <key>IOPCIMatch</key>          <string>0x94401002 0x944a1002</string>          <key>IOProbeScore</key>          <integer>65050</integer>          <key>IOProviderClass</key>          <string>IOPCIDevice</string>         <key>aty_config</key>          <dict>                 <key>CFG_NO_PP</key>                  <false/>                  <key>CFG_PAA</key>                  <integer>0</integer>                  <key>CFG_USE_USCN</key>                  <false/>          </dict>          <key>aty_properties</key>          <dict>                  <key>PP_GFXClockGatingEnabled</key>                  <integer>1</integer>          </dict> </dict> Et pour ATIRadeonX2000.kext
      <key>ATIRadeonX2000</key> <dict>         <key>ATIEnableWideBlitSupport</key>         <true/> <key>ATIUseTearingWideBlit</key> <false/> <key>CFBundleIdentifier</key> <string>com.apple.ATIRadeonX2000</string> <key>GpuDebugPolicy</key> <integer>0</integer> <key>IOCFPlugInTypes</key> <dict> <key>ACCF0000-0000-0000-0000-000a2789904e</key> <string>ATIRadeonX2000GA.plugin</string> </dict> <key>IOClass</key> <string>ATIRadeonX2000</string> <key>IODVDBundleName</key> <string>ATIRadeonX2000VADriver</string> <key>IOKitDebug</key> <integer>0</integer> <key>IOMatchCategory</key> <string>IOAccelerator</string> <key>IOPCIMatch</key> <string>0x94001002 0x94011002 0x94021002 0x94031002 0x95811002 0x95831002 0x95881002 0x94c81002 0x94c91002 0x95001002 0x95011002 0x95051002 0x95071002 0x95041002 0x95061002 0x95981002 0x94881002 0x95991002 0x95911002 0x95931002 0x94401002 0x94421002 0x944A1002 0x945A1002 0x94901002 0x949E1002 0x94801002 0x95401002 0x95411002 0x954E1002 0x954F1002 0x95521002 0x95531002 0x94a01002</string> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>IOSourceVersion</key> <string>8.24.11</string> <key>IOVARendererID</key> <integer>16908288</integer> <key>sensor-properties</key> <array> <dict> <key>device_type</key> <data> Z3B1LXNlbnNvcg== </data> <key>location</key> <string>GPU</string> <key>name</key> <string>gpu-sensor</string> <key>polling-period</key> <data> AAAAAQAAAAA= </data> <key>reg</key> <data> AAAAAg== </data> <key>sample-period</key> <data> AAAAAACYmAA= </data> <key>sensor-id</key> <data> AAAABg== </data> <key>version</key> <data> AAAAAg== </data> <key>zone</key> <data> AAAAAg== </data> </dict> </array </dict>  
      Et voici donc l'Info.plist de FakeSMC.kext dans son intégrité, vous pouvez jeter un oeil, histoire de voir à quoi cela ressemble :
       
      FakeSMC_Info.plist.zip
       
      Et pour les moins casse-têtes, voici FakeSMC.kext modifié que j'utilise pour charger les 2 kexts :
       
      FakeSMC.kext.zip
       
       
      Voilà, avec ceci, vous n'aurez plus besoin de savoir si oui ou non les kexts sont dans le kernelcache.
       
       
      Crédits attribués à :
       
      netkas  pour son incontournable QE_CI Exotic patch (même s'il n'importe plus son support)
       
      Slice  & co. pour leur bébé nommé Clover
       
      dmazar  pour son astuce avec FakeSMC.kext   (pour plus d'info, voir ici)
       
      duffs (rarement ici, plus sur le site de netkas) pour son astuce de comment patcher la partie binaire avec Clover, ce fût lors de la sortie de OS X Mavericks DP1
       
      nyolc8  pour le support de QE_CI Exotic patch pour Mavericks
       
      fantomas1  pour ......... pour ... quoi déjà ? Ah ben non ... non ... pour rien ...
    • By Slice
      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.
       
       
    • By apianti
      Just so you all know I actually have done something. I have pushed the source to both my github and to sourceforge, please commit to the experimental branch and I will merge it into the stable branch once it is safe. Also, nothing meaningful happens yet so don't get too excited. Only the Visual studio build works right now. I haven't set up the Xcode or Makefile builds yet, I'm trying to do them now.
       
      https://github.com/apianti/Clover
      https://sourceforge.net/p/cloverefiboot/Clover
       
      IA32/X64/ARM/ARM64 testing ISO (6/7/2018): Clover-3.0-experimental.iso
    • 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  selezionate OsxAptioFixDrv-64
                             *  :Se nel vostro sistema è presente una scheda grafica (discreta) della serie 9xx nVidia selezionate OsxAptioFix2Drv-64 al posto di  OsxAptioFixDrv-64 *
      ** OsxAptioFix2Drv :E' necessario per poter impostare CsrActiveConfig= 0x3 **
      ***OsxAptioFix3Drv oppure AptioMemory --> (consigliato) devono essere usati su hardware Skylake o successivi perché permettono alla nvram di lavorare correttamente
           (mi raccomando o uno o l'altro)
      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 guardate...
       Mojave in HFS 
       
       
       
      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
×