Jump to content
ErmaC

Clover Problems and Solutions

2,946 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 Teress
      To build a Hackintosh never was easier. If you want cheap Hackintosh and have it quickly and 100% working and without any knowledge how to tweak things, this video is right for you.
       
    • By fusion71au
      Clover r4747 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4747 for VMware.zip". Mount Clover-v2.4k-4747-X64 by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By superdooper71
      Hi all,
      I hope someone can help me as I am struggling with this bloody installation.
      I am running on several problems that I can't face : (
       
      First of all my config:
      Mobo: ASROCK H81M-DGS R2
      CPU: Intel Xeon E3-1220 v3 @3.10ghz
      RAM: 16gb DDR3 1600Mhz
      SSD: Crucial BX100 120Gb SSD
      Monitor: Hp 27w Hdmi
       
      POST Installation CLOVER
       
      Current Issues:
      • System will not boot (clover boot loader do not shows up) from SSD
         - System boot only with USB stick
      • Screen Resolution is only 1024x768
      • Monitor recognised as 17" instead of 24"
      • Monitor identified as secondary
      • Grafic Card Geforce GT710 shows 0 Mb
      • System info do not match Config.plistin Clover
       
      I attach screenshot of System Info, Kext in Clover, Resolution etc etc.
       
      Please can someonhelp me?
       
      Please can you tell me what is the Clover Parameter to activate when installing Clover  (Clover_v2.4k_r4722) into Boot Disk?
       
      I hope someone can help me out of this little troble: )
       
      Cheers
      Franco
       
      system info.tiff
      kext.tiff
      resolution.tiff
      system.tiff
      config.plist
    • 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 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






    • By shmn
      Hi, I have been trying to follow @RehabMan 's guide to disable my dGPU ( https://www.tonymacx86.com/threads/guide-disabling-discrete-graphics-in-dual-gpu-laptops.163772/ ) for two days now, but haven't found a way to disable my 1080 Ti on my desktop Clover hack.

      I have a dual-boot (Win/Mac) machine on a Z370 Aorus 7. Since there's no nvidia drivers for Mojave atm, I want to stick with the iGPU under Mac, but still use the 1080 Ti under Win.

      The hack boots just fine when I remove the 1080 Ti, if it's plugged in via PCIe I get a kernel panic.
      Please find attached my ACPI folder, my clover config.plist and the kernel panic details.

      Might there even be a less hacky way than patching these ACPI files? I appreciate any kind of support! Thanks!
      ACPI.zip
      config.plist

      systemReport.txt
×