Jump to content

Clover General discussion


ErmaC
29,866 posts in this topic

Recommended Posts

Here's some background info what bootbase.efi does. Let's start with the booter configuration:

 

kBootArgsFlagCSRActiveConfig (0x8/8) informs OS X that the device has a valid configuration.

 

kBootArgsFlagCSRConfigMode (0x10/16) informs OS X that the device is in configuration mode.

 

kBootArgsFlagCSRBoot (0x20/32) asks OS X to allow everything.

 

That, along with the special flag CSR_ALLOW_DEVICE_CONFIGURATION (0x80/128) is used by bootbase.efi (and nothing else) for the installation process. If the installation process is ready, then the normal boot.efi is being used by bless for the next reboot. After that only kBootArgsFlagCSRActiveConfig (0x8/8) is used.

 

You can do a grep for 'bootbase.efi' in /.IABootfiles/boot.efi or /OS X Install Data/boot.efi (depending on the type of installation) and see for yourself. bootbase.efi has SIP disabled with the above flags ;)

 

p.s. Now you say; but I don't see 0x80 in csr-active-config. Right. masked with 0x7f. Thanks Apple!

 

Let's clear things up properly. Piker, what is the right setting for the system installation process? The correct values?

 
After installation, we should put values on which "BooterConfig" and "CsrActiveConfig"?
 
And when we perform a "MAINTENANCE" in the system, type: remake the kernel cache, what should we put it?
 
I'm thinking of doing as follows:
 
Installation by "penboot": BooterConfig = 0x38 and CsrActiveConfig = 0x80;
 
In normal use (day by day): BooterConfig = 0x8 and CsrActiveConfig = 0x0;
 
MAINTENANCE make system boot with "Penboot".
 
Or am I making nonsense?
 
Thanks.
  • Like 3
Link to comment
Share on other sites

Another subject :

 

Did anyone managed to get genuine Apple Magic Mouse  / Apple Keyboard (or other BT mice/keyboards) to work with Clover GUI ?

 

My configuration doesn't seem to work (Clover r3270 , AW-CE123H on mini PCIe slot), but some other configurations seem to work ( BCM94360CD ...)

 

Maybe it's only BIOS related ...

Link to comment
Share on other sites

I'm having problems starting Windows from Clover on a legacy boot.

 

I have three drives on my Gigabyte GA-P67A-UD3P-B3 legacy BIOS machine. One with OS X Yosemite and Clover, one with legacy install of Windows7 x64 and a non-boot NTFS drive:

/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *250.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS OSX                     249.2 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *120.0 GB   disk1
   1:               Windows_NTFS Disk C                  120.0 GB   disk1s1
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *500.1 GB   disk2
   1:               Windows_NTFS Disk D                  500.1 GB   disk2s1

I have no problems starting either OS X or Windows straight from BIOS. I can start OS X from Clover, but I get a black screen when launching Windows from Clover. I have LegacyBiosDefault option in my config,

 

 

 

<key>Boot</key>
<dict>
   <key>Arguments</key>
   <string>-v arch=x86_64 dart=0 kext-dev-mode=1</string>
   <key>Debug</key>
   <false/>
   <key>DefaultVolume</key>
   <string>OSX</string>
   <key>Legacy</key>
   <string>LegacyBiosDefault</string>
   <key>LegacyBiosDefaultEntry</key>
   <integer>2</integer>
   <key>Secure</key>
   <false/>
   <key>Timeout</key>
   <integer>5</integer>
   <key>XMPDetection</key>
   <false/>
</dict>

 

which as far as I understand allows booting another drive from MBR. I've tried PBR and PBRTest also with no success. I have either eternal Clover GUI Windows logo screen with LegacyBiosDefault or "Press Ctrl+Alt+Del" with PBR method.

 
Also, Clover names both of my NTFS drives as "Legacy HD1". Aren't they supposed to be different?
 
So anyone has clues what's wrong with my settings?

 

Bootlog:

 

0:100  0:100  MemLog inited, TSC freq: 3292521189
0:100  0:000  
0:100  0:000  Now is 3.10.2015,  13:26:34 (GMT+2047)
0:100  0:000  Starting Clover rev 3270 on TianoCore.org EFI
0:100  0:000  SelfDevicePath=PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,GPT,0603AC4E-B2B6-40AB-8116-00DD9C9735EE,0x28,0x64000) @DE7D4118
0:100  0:000  SelfDirPath = \EFI\BOOT
0:100  0:000  Total Memory Slots Count = 4
0:100  0:000  Type 17 Index = 0
0:100  0:000  SmbiosTable.Type17->Speed = 1333MHz
0:100  0:000  SmbiosTable.Type17->Size = 4096MB
0:100  0:000  SmbiosTable.Type17->Bank/Device = Bank0/1 A0
0:100  0:000  Type 17 Index = 1
0:100  0:000  SmbiosTable.Type17->Speed = 1333MHz
0:100  0:000  SmbiosTable.Type17->Size = 4096MB
0:100  0:000  SmbiosTable.Type17->Bank/Device = Bank2/3 A1
0:100  0:000  Type 17 Index = 2
0:100  0:000  SmbiosTable.Type17->Speed = 1333MHz
0:100  0:000  SmbiosTable.Type17->Size = 4096MB
0:100  0:000  SmbiosTable.Type17->Bank/Device = Bank4/5 A2
0:100  0:000  Type 17 Index = 3
0:100  0:000  SmbiosTable.Type17->Speed = 1333MHz
0:100  0:000  SmbiosTable.Type17->Size = 4096MB
0:100  0:000  SmbiosTable.Type17->Bank/Device = Bank6/7 A3
0:100  0:000  Boot status=0
0:100  0:000  Clover revision: 3270  running on P67A-UD3P-B3
0:100  0:000  ... with board P67A-UD3P-B3
0:100  0:000  CPU Vendor = 756E6547 Model=206A7
0:100  0:000  The CPU supported turbo
0:100  0:000  BrandString = Intel® Core i5-2500K CPU @ 3.30GHz
0:100  0:000  MSR 0xE2 before patch 1E000403
0:100  0:000  MSR 0xE4              00020414
0:100  0:000  MSR 0xCE              00001000_70012100
0:100  0:000  non-usable FLEX_RATIO = F0000
0:100  0:000  corrected FLEX_RATIO = E0000
0:100  0:000  MSR 0x1B0             00000000
0:100  0:000  FSBFrequency=127MHz DMIvalue=100000kHz
0:100  0:000  Corrected FSBFrequency=100MHz
0:100  0:000  Vendor/Model/Stepping: 0x756E6547/0x2A/0x7
0:100  0:000  Family/ExtFamily: 0x6/0x0
0:100  0:000  MaxDiv/MinDiv: 33.0/16
0:100  0:000  Turbo: 42/42/42/42
0:100  0:000  Features: 0xBFEBFBFF
0:100  0:000  Threads: 4
0:100  0:000  Cores: 4
0:100  0:000  FSB: 100 MHz
0:100  0:000  CPU: 4200 MHz
0:100  0:000  TSC: 4200 MHz
0:100  0:000  PIS: 400 MHz
0:100  0:000  PCI (00|00:00.00) : 8086 0100 class=060000
0:100  0:000  PCI (00|00:01.00) : 8086 0101 class=060400
0:100  0:000  PCI (00|01:00.00) : 1002 68BA class=030000
0:100  0:000  Found Radeon model=ATI Radeon HD 6770 Series
0:100  0:000  PCI (00|01:00.01) : 1002 AA58 class=040300
0:100  0:000  PCI (00|00:16.00) : 8086 1C3A class=078000
0:100  0:000  PCI (00|00:1A.00) : 8086 1C2D class=0C0320
0:100  0:000  PCI (00|00:1B.00) : 8086 1C20 class=040300
0:100  0:000  PCI (00|00:1C.00) : 8086 1C10 class=060400
0:100  0:000  PCI (00|02:00.00) : 1033 0194 class=0C0330
0:100  0:000  PCI (00|00:1C.01) : 8086 1C12 class=060400
0:100  0:000  PCI (00|03:00.00) : 1033 0194 class=0C0330
0:100  0:000  PCI (00|00:1C.02) : 8086 1C14 class=060400
0:100  0:000  PCI (00|04:00.00) : 10EC 8168 class=020000
0:100  0:000  LAN 0, Vendor=10EC, MMIO=DE00
0:100  0:000  PCI (00|00:1C.03) : 8086 244E class=060401
0:100  0:000  PCI (00|05:00.00) : 1283 8892 class=060401
0:100  0:000  PCI (00|00:1D.00) : 8086 1C26 class=0C0320
0:100  0:000  PCI (00|00:1F.00) : 8086 1C46 class=060100
0:100  0:000  PCI (00|00:1F.02) : 8086 1C02 class=010601
0:100  0:000  PCI (00|00:1F.03) : 8086 1C22 class=0C0500
0:100  0:000  Clover load options size = 0 bytes
0:126  0:026  Using OEM config.plist at path: EFI\CLOVER\config.plist
0:126  0:000  EFI\CLOVER\config.plist loaded: Success
0:143  0:016  Found theme directory: embedded
0:143  0:000  Found theme directory: os_one
0:147  0:004  Found theme directory: random
0:147  0:000  Loading early settings
0:147  0:000  timeout set to 5
0:147  0:000  Custom boot CUSTOM_BOOT_DISABLED (0x0)
0:147  0:000  KextsToPatch: 3 requested
0:147  0:000  KextToPatch 0: AMDRadeonX3000 Info.plist patch, data len: 8
0:147  0:000  KextToPatch 1: AMD5000Controller Info.plist patch, data len: 8
0:147  0:000  KextToPatch 2: AppleAHCIPort (External icons patch) Kext bin patch, data len: 8
0:147  0:000  Default theme: embedded
0:147  0:000  Hiding entries with string \EFI\BOOT\BOOTX64.EFI
0:147  0:000  LoadDrivers() start
0:154  0:006  Loading FSInject-64.efi  status=Success
0:162  0:007  Loading HFSPlus.efi  status=Success
0:162  0:000   - driver needs connecting
0:162  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
0:170  0:007  1 drivers needs connecting ...
0:170  0:000  PlatformDriverOverrideProtocol->GetDriver overriden
0:170  0:000  HFS+ driver loaded 
0:170  0:000  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:309  0:139  LoadDrivers() end
0:309  0:000  Dump SMC keys from NVRAM:
0:309  0:000  SetMaxResolution: found best mode 4: 1280x1024
0:995  0:685  Video mode change to mode #4: Success
0:995  0:000   - set
0:995  0:000  Console modes reported: 3, available modes:
0:995  0:000    Mode 1: 80x25 (current mode)
0:995  0:000    Mode 3: 100x31
0:995  0:000  SetScreenResolution: 1280x1024 - already set
1:059  0:063  reinit: self device path=PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,GPT,0603AC4E-B2B6-40AB-8116-00DD9C9735EE,0x28,0x64000)
1:059  0:000  ScanSPD() start
1:059  0:000  SMBus CmdReg: 0x3
1:059  0:000  Scanning SMBus [8086:1C22], mmio: 0xFBFFB004, ioport: 0x500, hostc: 0x1
1:059  0:000  Slots to scan [8]...
1:074  0:014  SPD[0]: Type 11 @0x50 
1:082  0:008  DDR speed 1333MHz 
1:083  0:000  Slot: 0 Type 24 4096MB 1333MHz Vendor=Kingston PartNo=9905403-400.A00LF SerialNo=030F030203020C01 
1:097  0:014  SPD[1]: Type 11 @0x51 
1:106  0:008  DDR speed 1333MHz 
1:106  0:000  Slot: 1 Type 24 4096MB 1333MHz Vendor=Kingston PartNo=9905403-400.A00LF SerialNo=04010302020D0C01 
1:120  0:014  SPD[2]: Type 11 @0x52 
1:129  0:008  Found module with XMP version 1.2DDR speed 1600MHz 
1:129  0:000  Slot: 2 Type 24 4096MB 1600MHz Vendor=Nanya Technology PartNo=M2X4G64CB8HG5N-DG SerialNo=04010E06030C0005 
1:143  0:014  SPD[3]: Type 11 @0x53 
1:152  0:008  Found module with XMP version 1.2DDR speed 1600MHz 
1:152  0:000  Slot: 3 Type 24 4096MB 1600MHz Vendor=Nanya Technology PartNo=M2X4G64CB8HG5N-DG SerialNo=0C020004030D0003 
1:182  0:030  ScanSPD() end
1:193  0:010  Get Acpi Tables List from RSDT:
1:193  0:000   Found table: FACP  GBTUACPI len=116
1:193  0:000   Found table: MSDM  GBTUACPI len=85
1:193  0:000   Found table: HPET  GBTUACPI len=56
1:193  0:000   Found table: MCFG  GBTUACPI len=60
1:193  0:000   Found table: ASPT  PerfTune len=52
1:193  0:000   Found table: SSPT  SsptHead len=9116
1:193  0:000   Found table: EUDS   len=192
1:193  0:000   Found table: MATS   len=52
1:193  0:000   Found table: TAMG  GBT   B0 len=2690
1:193  0:000   Found table: APIC  GBTUACPI len=188
1:193  0:000   Found table: SSDT  PPM RCM  len=8012
1:193  0:000   Found table: MATS  MATS RCM len=42329
1:193  0:000  Calibrated TSC frequency =3292521189 =3292MHz
1:193  0:000  Loading main settings
1:193  0:000  Read NVCAP:0000000000000000000000000000000000000000
1:193  0:000  Config set Fixes will override FixMask mask!
1:193  0:000     final mask=00000010
1:193  0:000  Config set EnableC6: +
1:193  0:000  Config set C3Latency: 999
1:193  0:000  Config set MinMultiplier=16
1:193  0:000  Config set ChassisType=0xD
1:193  0:000  Config set QPI = 0 disable table132
1:193  0:000  Config set CpuFreq=3309MHz
1:193  0:000  Config set CpuType=603
1:193  0:000  Config set BusSpeed=100294kHz
1:194  0:000  found 9 volumes with blockIO
1:194  0:000   0. Volume:
1:194  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)
1:194  0:000    Result of bootcode detection: bootable unknown (legacy)
1:194  0:000   1. Volume:
1:194  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)
1:196  0:002    Result of bootcode detection: bootable unknown (legacy)
1:196  0:000   2. Volume:
1:196  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0x0,0x0)
1:196  0:000    found optical drive
1:196  0:000   3. Volume:
1:196  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)
1:196  0:000    Result of bootcode detection: bootable unknown (legacy)
1:196  0:000   4. Volume:
1:196  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,GPT,0603AC4E-B2B6-40AB-8116-00DD9C9735EE,0x28,0x64000)
1:196  0:000    Result of bootcode detection: bootable Clover (clover)
1:222  0:026    This is SelfVolume !!
1:222  0:000   5. Volume:
1:222  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,9AE164B4-0AE2-412F-A638-365C18401685,0x64028,0x1D02BA00)
1:222  0:000   6. Volume:
1:222  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,8C1D5F80-2435-46FD-A142-9DBF3D5248B4,0x1D08FA28,0x135F20)
1:222  0:000   7. Volume:
1:222  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(1,MBR,0x3E5E86E5,0x3F,0xDF93782)
1:223  0:000    Result of bootcode detection: bootable Windows (vista,win)
1:223  0:000   8. Volume:
1:223  0:000    PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(1,MBR,0x8A6F77EC,0x4,0x3A385D74)
1:223  0:000    Result of bootcode detection: bootable Windows (win)
1:223  0:000   using embedded theme
1:223  0:000  Choosing theme <null string>
1:223  0:000  Custom legacy start
1:223  0:000  Custom legacy end
1:223  0:000  Scanning legacy ...
1:223  0:000   0: 'Whole Disc Boot' (legacy) not legacy
1:223  0:000   1: 'Whole Disc Boot' (legacy) not legacy
1:223  0:000   2: 'Whole Disc Boot' (legacy) not legacy
1:223  0:000   3: 'Whole Disc Boot' (legacy) not legacy
1:223  0:000   4: 'EFI' (clover) add legacy
1:223  0:000   added 'Boot Clover from EFI' OSType=3 Icon=clover
1:223  0:000   5: 'OSX' (legacy) not legacy
1:223  0:000   6: 'Recovery HD' (legacy) not legacy
1:223  0:000   7: 'Legacy HD1' (vista,win) add legacy
1:223  0:000   added 'Boot Windows from Legacy HD1' OSType=2 Icon=vista,win
1:223  0:000   8: 'Legacy HD1' (win) add legacy
1:223  0:000   added 'Boot Windows from Legacy HD1' OSType=2 Icon=win
1:223  0:000  Custom entries start
1:223  0:000  Custom entries finish
1:223  0:000  Scanning loaders...
1:223  0:000   0: 'Whole Disc Boot' no file system
1:223  0:000   1: 'Whole Disc Boot' no file system
1:223  0:000   2: 'Whole Disc Boot' no file system
1:223  0:000   3: 'Whole Disc Boot' no file system
1:223  0:000   4: 'EFI'
1:249  0:025   5: 'OSX'
1:279  0:030      AddLoaderEntry for Volume Name=OSX
1:328  0:049      Check if volume Is Hibernated:
1:328  0:000      Check sleep image 'by signature':
1:371  0:042      read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Not Found
1:371  0:000      using default sleep image name = \private\var\vm\sleepimage
1:399  0:028      sleepimage not found -> Not Found
1:399  0:000       hibernated: no - sign
1:400  0:000   6: 'Recovery HD'
1:419  0:019      AddLoaderEntry for Volume Name=Recovery HD
1:425  0:005   7: 'Legacy HD1' no file system
1:425  0:000   8: 'Legacy HD1' no file system
1:425  0:000  Custom tool start
1:425  0:000  Custom tool end
1:425  0:000  GetEfiBootDeviceFromNvram: efi-boot-device-data not found
1:425  0:000  EfiBootVolume not found
1:425  0:000   found entry 3. 'Boot Mac OS X from OSX', Volume 'OSX', DevicePath 'PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,9AE164B4-0AE2-412F-A638-365C18401685,0x64028,0x1D02BA00)\System\Library\CoreServices\boot.efi'
1:425  0:000  DefaultIndex=3 and MainMenu.EntryCount=9
1:504  0:078  Found Mouse device:
1:504  0:000  GUI ready
8:571  7:066  BootOption of the entry is empty
8:571  0:000  Removed efi-boot-device-data variable: Not Found
8:627  0:055  boot from partition HD(1,MBR,0x3E5E86E5,0x3F,0xDF93782)
8:627  0:000  starting from 0x3F LBA 
8:627  0:000  gEfiLegacy8259ProtocolGuid found
8:629  0:002  PBR after readDisk:
8:629  0:000  0000: EB 52 90 4E 54 46 53 20 20 20 20 00 02 08 00 00 
8:629  0:000  0010: 00 00 00 00 00 F8 00 00 3F 00 FF 00 3F 00 00 00 
8:629  0:000  0020: 00 00 00 00 80 00 80 00 80 37 F9 0D 00 00 00 00 
8:629  0:000  0030: 00 00 0C 00 00 00 00 00 02 00 00 00 00 00 00 00 
8:629  0:000  Reset disk controller 0x80

 

 
 

config.plist.zip

Link to comment
Share on other sites

Is there an issue with build 3270?

 

--

 

i'am new to Clover - first Time used with ElCap

 

and i can confirm there's a misbehaviour with 3270 & 3276 ( even re-compiled ),

 

but sometime the system won't start (no changes were made at all to config.plist or system).

 

after changing a theme i get a kernel panic with above mentioned versions.

 

only success with 3264.

 

--

 

OR MAYBE my system is little bit to old - it's time to get a 6 core ;-)

 

adapted my old settings to config.plist (also changed from 10,1 to 3,1) everything's perfect now  :rofl:

 

thx to all Clover devs.  :thumbsup_anim:

Link to comment
Share on other sites

Guys, I've got a question for you, as well.

 

When I upgraded to El Capitan, I removed my previous Yosemite partition and expanded the one for El Capitan.

 

Now, the problem is that, by doing that, the Recovery partition that was previously for Yosemite is still there. And now, when I boot my computer, I've got El Capitan, the OS partition, and 2 Recovery partitions.

 

Which leads me to these two questions:

1. How do I know which one of the two is the correct one for El Capitan?

2. How do I remove the one I don't need?

Link to comment
Share on other sites

You can remove the partition using diskutil.

First "diskutil list" to see what partition to remove and than "diskutil eraseVolume HFS+ Blank /dev/diskXsY"

Yeah... The problem is repartitioning after. This seems to be a lot more complicated than it has to be. But yes, removing the partition was the easiest part. And I'm already done with that.

 

Now I'm just making a backup of my current stuff so I can "journal" (although they ARE already journaled) my partitions and repartition so I can have everything nice and clean. :)

 

Thank you.

Link to comment
Share on other sites

Let's clear things up properly. Piker, what is the right setting for the system installation process? The correct values?

 

After installation, we should put values on which "BooterConfig" and "CsrActiveConfig"?

 

And when we perform a "MAINTENANCE" in the system, type: remake the kernel cache, what should we put it?

 

I'm thinking of doing as follows:

 

Installation by "penboot": BooterConfig = 0x38 and CsrActiveConfig = 0x80;

 

In normal use (day by day): BooterConfig = 0x8 and CsrActiveConfig = 0x0;

 

MAINTENANCE make system boot with "Penboot".

 

Or am I making nonsense?

 

Thanks.

Hombre!

 

I wasn't talking Spanish now was I? Look here http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page-417?do=findComment&comment=2172224

 

That's the hex/decimal values you need.

  • Like 1
Link to comment
Share on other sites

Hombre!

 

I wasn't talking Spanish now was I? Look here http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page-417?do=findComment&comment=2172224

 

That's the hex/decimal values you need.

 

Ok, so I will do this:

Penboot: BooterConfig = 0x38 and CsrActiveConfig = 0x80
 
Boot the normal system (Use): BooterConfig = 0x8 and CsrActiveConfig = 0x0
 
Can it be like this?
 
Thanks.
Link to comment
Share on other sites

Ok, so I will do this:

Penboot: BooterConfig = 0x38 and CsrActiveConfig = 0x80

 

Boot the normal system (Use): BooterConfig = 0x8 and CsrActiveConfig = 0x0

 

Can it be like this?

 

Thanks.

For the normal boot you may need CsrActiveConfig=0x1 otherwise unsigned kext may not loadm but that depends on the kind of kext injection Clover supports, and if you use it.
  • Like 1
Link to comment
Share on other sites

You can merge that partition to an existing one with diskutil.

Yeah, I know that too. But that would pretty much double the size of the same partition, for no good reason whatsoever. Not to mention that, on the next OS, it will probably create a new Recovery partition and so on so forth. So no. I don't think that merging really helps, on the long term.

 

Now, since the new Disk Utility sucks balls through a straw, I had to do 99% of this work on Ubuntu.

 

Result?

 

Cleeeean :D

post-1303722-0-77277900-1443909040_thumb.png

Link to comment
Share on other sites

You could have merge it to "Tools" or "ElCapitan" partition. :)

 

You can't merge it to a "left side" partition easily... :)

It would have taken too much time to resize (it would have needed to move a lot of data to the left, because the partition was almost full, and then resize). And Disk Utility said it can't resize them cause the partitions were not "journaled" (of course they were). I think this is a bug...

 

Anyway, so what I did was to backup Tools (that took a while too, but not as much as it would have taken if I were to wait for the resize process to finish), deleted all the partitions that I didn't need (or had backup of), apparently I had a Microsoft kind of partition there as well, that I didn't use, since I have no Microsoft OS on this particular HDD, recreated Tools, and restored the data onto it.

 

Anyway, I'm glad it's all fine now. And thank you for sharing your ideas.

Link to comment
Share on other sites

When the Clover theme arrives with all the settings and I go to the CPU tuning section, I see that Enable C6 is enabled. But when I check the settings with Clover Configurator, I see that it is not chosen. 

Why it is always enabled although I have chosen it not to be so? 

Link to comment
Share on other sites

When the Clover theme arrives with all the settings and I go to the CPU tuning section, I see that Enable C6 is enabled. But when I check the settings with Clover Configurator, I see that it is not chosen.

 

Why it is always enabled although I have chosen it not to be so?

Probably because you need it?
Link to comment
Share on other sites

Good point! I dont know because I dont use sleep, I have disabled it from the OSX preferences. 

You see, C states are used, for as far as I know, for sleep/hibernation. Basically anything that's not considered a "fully ON" PC. Except for C0 state (if I'm not mistaken), which is also known as "halt". Basically, the computer (or rather the CPU) is OFF, and not suspended in any kind of "hibernation/sleep" mode. I don't know what was your reason for disabling it, but you probably shouldn't have? :) Just saying.

  • Like 1
Link to comment
Share on other sites

I also noticed it's selected automatically, even if you don't need it and even ssdt generation is set to flase. I use custom ssdt so I specified EnableC6=false.

Same thing with AppleRTC patching.

I assume it's a fail-safe, in case you don't have alternative solutions. And, to be honest, I like it. I think it's a good thing to have backups. Especially if you're a new user. It doesn't bring any harm. Same for SSDT/DSDT. I don't need a custom one, cause all my patches are made (and can be easily enabled/disabled) from Clover. I prefer to have as little things to manage, as possible.  Less things to manage = smaller chance of failure. Adding custom DSDT to the equation won't make things any easier. On the contrary. So I really like it this way.

Link to comment
Share on other sites

×
×
  • Create New...