Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,866 posts in this topic

Recommended Posts

ameris_cyning
ameris_cyning
Posted
Posted

 

I think you should take into account commit 2322

           case CPU_MODEL_IVY_BRIDGE:
           case CPU_MODEL_HASWELL:
           case CPU_MODEL_IVY_BRIDGE_E5:  
+          case CPU_MODEL_HASWELL_MB:
+          case CPU_MODEL_HASWELL_ULT:
+          case CPU_MODEL_HASWELL_ULX:

 

I am sorry, can you please elaborate on that? I am lost with what you said.

Link to comment
Share on other sites
pauℓzurrr.
pauℓzurrr.
Posted
Posted

Could someone tell me if i missed something? I've got a GA-Z77-DS3H motherboard. After i updated Clover to the latest version (Clover_v2k_r2298.zip)i'm unable to auto boot my OSX Mountain Lion HDD.

I did not made any changes to the config file. What could the problem be what's causing Clover not to auto boot all of the sudden?

Link to comment
Share on other sites
ameris_cyning
ameris_cyning
Posted
Posted

Could someone tell me if i missed something? I've got a GA-Z77-DS3H motherboard. After i updated Clover to the latest version (Clover_v2k_r2298.zip)i'm unable to auto boot my OSX Mountain Lion HDD.

I did not made any changes to the config file. What could the problem be what's causing Clover not to auto boot all of the sudden?

 

Try this:

 

Open terminal and type "sudo nvram -c" (without the quotes)

 

Enter password then reboot

Link to comment
Share on other sites
comwave7
comwave7
Posted
Posted

Could someone tell me if i missed something? I've got a GA-Z77-DS3H motherboard. After i updated Clover to the latest version (Clover_v2k_r2298.zip)i'm unable to auto boot my OSX Mountain Lion HDD.

I did not made any changes to the config file. What could the problem be what's causing Clover not to auto boot all of the sudden?

How about checking your config.plist?

For some reason, the DefaultVolume under Boot might have been changed from your ML HDD to MacHDD, the Clover default.

If it's the case, you should change it to your ML HDD again.

Link to comment
Share on other sites
pauℓzurrr.
pauℓzurrr.
Posted
Posted

The latest Clover is Clover_v2k_r2330  B)

 

The problem persists with this version as well.

 

How about checking your config.plist?

For some reason, the DefaultVolume under Boot might have been changed from your ML HDD to MacHDD, the Clover default.

If it's the case, you should change it to your ML HDD again.

 

Yes i've checked the config.plist. Which has the DefaultVolume for my hdd, "Macintosh HD"

Also there are two boot options when i start the pc.

"Boot UEFI internal from EFI" and "Boot Mac OS X from Macintosh HD"

Not sure if the first one was present or visible for me with the other versions of clover..

Link to comment
Share on other sites
ameris_cyning
ameris_cyning
Posted
Posted

The problem persists with this version as well.

 

 

Yes i've checked the config.plist. Which has the DefaultVolume for my hdd, "Macintosh HD"

Also there are two boot options when i start the pc.

"Boot UEFI internal from EFI" and "Boot Mac OS X from Macintosh HD"

Not sure if the first one was present or visible for me with the other versions of clover..

 

Open up the Clover prefpane 

 

On the tab "NVRAM variables", set "Save NVRAM contents to disk" to always

 

Reboot.

 

Reopen Cloverprefpane

 

Set it to Auto

 

Reboot

 

It should work.

Link to comment
Share on other sites
comwave7
comwave7
Posted
Posted

With auto boot I mean the system just boots to the desktop instead of "hanging" at the Clover screen until i choose the HDD to boot.

I've attached my config.plist! Thanks 

 

Why don't you change your GUI > Timeout to 0, and SystemParameters > boot-args to "npci=0x3000 slide=0"?

Have you tried it already?

 

Edited:

As an alternative to the recommendation from Maniac10, you can just delete the current EFI folder after copying it into another place and reinstall the latest Clover. 

And modify the new config.plist according to your individual requirements based on your previous one.

 

When you have a pre-installed config.plist in EFI folder, Clover doesn't touch it.

So you have to delete your config.plit before installing a new revision to get a proper config.plist for the new revision.

  • Like 1
Link to comment
Share on other sites
Maniac10
Maniac10
Posted
Posted

With auto boot I mean the system just boots to the desktop instead of "hanging" at the Clover screen until i choose the HDD to boot.

I've attached my config.plist! Thanks 

 

attachicon.gifconfig.plist.zip

 

Your whole config is outdated, you should run it through the Clover Configuration Converter (google it).

 

* The GUI section changed

* The default volume is set in the Boot section

Link to comment
Share on other sites
pauℓzurrr.
pauℓzurrr.
Posted
Posted

Your whole config is outdated, you should run it through the Clover Configuration Converter (google it).

 

* The GUI section changed

* The default volume is set in the Boot section

 

This is getting fun, after running my plist thru the Configuration Converter, I'm not seeing any drive to boot with clover...

Link to comment
Share on other sites
todesto
todesto
Posted
Posted

after number of testing and clean installs, i find my system will sleep and wake fine first time, but it will reboot on wake on second sleep. I have tried on other partition with 10.9 so this maverick power management and Z68 which I have does not work well with clover. or is this the issue I am only having?

Link to comment
Share on other sites
ameris_cyning
ameris_cyning
Posted
Posted

after number of testing and clean installs, i find my system will sleep and wake fine first time, but it will reboot on wake on second sleep. I have tried on other partition with 10.9 so this maverick power management and Z68 which I have does not work well with clover. or is this the issue I am only having?

Have you set darkwake=0?

Link to comment
Share on other sites
Fab1Man
Fab1Man
Posted
Posted

I was looking at my Console.log because EFI is still mounted although it's explicitly set at NO.

 

What is this for?

0:105  0:005  ConfigPlistPath: EFI\CLOVER\WINDOWS.plist
0:105  0:000  Oem WINDOWS.plist not found at path: EFI\CLOVER\WINDOWS.plist
0:105  0:000  Error loading config.plist! Status=Not Found
0:105  0:000  EFI\CLOVER\WINDOWS.plist not loaded with name from LoadOptions: Not Found
0:105  0:000  ConfigPlistPath: EFI\CLOVER\config.plist
0:106  0:001  Using OEM config.plist at path: EFI\CLOVER\OEM\Z77X-UD5H\UEFI\config.plist
0:107  0:000  EFI\CLOVER\OEM\Z77X-UD5H\UEFI\config.plist loaded: Success

And then it recognized my Data drive as BootcampHD, which it isn't. Any way to adjust this?

0:534  0:000  Loading nvram.plist from Vol 'Macintosh SSD' - loaded, size=2705
0:535  0:000  PutNvramPlistToRtVars ...
0:535  0:000   Adding Key: BackgroundClear: Data: Size = 4: Success
0:535  0:000   Adding Key: BootCampHD: Data: Size = 32: Success
0:535  0:000   Adding Key: Clover.BackupDirOnDestVol: Data: Size = 2: Success
0:535  0:000   Adding Key: Clover.KeepBackupLimit: Data: Size = 1: Success
0:535  0:000   Adding Key: Clover.LogEveryBoot: Data: Size = 3: Success
0:535  0:000   Adding Key: Clover.LogLineCount: Data: Size = 4: Success
0:535  0:000   Adding Key: Clover.MountEFI: Data: Size = 3: Success
0:535  0:000   Adding Key: Clover.Theme: Data: Size = 6: Success
0:535  0:000   Skipping EmuVariableUefiPresent
0:535  0:000   Skipping OsxAptioFixDrv-RelocBase
0:535  0:000   Adding Key: SystemAudioVolume: Data: Size = 1: Success
0:535  0:000   Adding Key: bluetoothActiveControllerInfo: Data: Size = 16: Success
0:535  0:000   Adding Key: boot-gamma: Data: Size = 118: Success
0:535  0:000   Adding Key: boot-image: Data: Size = 56: Success
0:535  0:000   Adding Key: efi-boot-device: Data: Size = 216: Success
0:535  0:000   Adding Key: efi-boot-device-data: Data: Size = 74: Success
0:535  0:000   Adding Key: fmm-computer-name: Data: Size = 15: Success
0:535  0:000   Adding Key: fmm-mobileme-token-FMM: Data: Size = 518: Success
0:535  0:000   Adding Key: platform-uuid: Data: Size = 16: Success
0:535  0:000   Adding Key: security-mode: String: Size = 4, Val = 'none': Success

I'm still unable to use the StartupDisk preference pane to set Windows as default. It always uses the last booted partition. Anyone know how to fix this?

Link to comment
Share on other sites
toleda
toleda
Posted
Posted

Running 2236 successfully on a Z87I-Deluxe/HD4600/HD7750, use SSDT-1 (HDEF/IGPU+HDAU/GFX0+HDAU) to enable graphics/audio. Installed 2330, with everything else the same, IGPU+HDAU are not patched.  Both debug logs show:

148:963  0:717  Inserting SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success

 

2236/IOReg has IGPU+HDA (as expected), 2330/IOReg has GFX0 and BOD3 (native).  Config.plist are the same.  

 

Suggestions?

 

 

2236-2330_files.zip

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Running 2236 successfully on a Z87I-Deluxe/HD4600/HD7750, use SSDT-1 (HDEF/IGPU+HDAU/GFX0+HDAU) to enable graphics/audio. Installed 2330, with everything else the same, IGPU+HDAU are not patched.  Both debug logs show:

148:963  0:717  Inserting SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success

 

2236/IOReg has IGPU+HDA (as expected), 2330/IOReg has GFX0 and BOD3 (native).  Config.plist are the same.  

 

Suggestions?

But sorry, IGPU and HDAU are ACPI names and written in DSDT/SSDT. As you are not using DSDT patch by Clover so it is not Clover mistake.

Check if your DSDT is the same in both cases.

About SSDT in first log I see

146:089  0:356  Drop tables from Xsdt, SIGN=SSDT TableID=
146:446  0:357   Xsdt has tables count=8 
146:807  0:360   Table: SSDT  Cpu0Ist  dropped
147:163  0:356   Table: SSDT  SataTabl  dropped
147:528  0:365   Table: SSDT  SaSsdt   dropped
147:889  0:360  corrected XSDT length=76
148:245  0:356  Inserting SSDT.aml from EFI\CLOVER\ACPI\patched ... Success
148:963  0:717  Inserting SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
149:681  0:718  Inserting SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success
150:398  0:717   CPUBase=0 and ApicCPUBase=1 ApicCPUNum=8

It means DropOemSsdt is present.

In second log I see no such drops

16:708  0:006  Drop tables from Xsdt, SIGN=SSDT TableID=CpuPm Length=2776
16:715  0:006   Xsdt has tables count=9 
16:722  0:006   Table: SSDT  CpuPm  2776 dropped
16:729  0:006  corrected XSDT length=100
16:735  0:006  Patch table: SSDT  Cpu0Ist
16:742  0:006   SSDT len = 0x539
16:749  0:006  Patch table: SSDT  SataTabl
16:755  0:006   SSDT len = 0x36D
16:762  0:006  Patch table: SSDT  SaSsdt 
16:774  0:012   SSDT len = 0x329E
16:781  0:006  Drop tables from Xsdt, SIGN=XXXX TableID= Length=0
16:788  0:006   Xsdt has tables count=8 
16:795  0:006  corrected XSDT length=100
16:801  0:006  Inserting SSDT.aml from EFI\CLOVER\ACPI\patched ... Success
16:817  0:015  Inserting SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
16:833  0:015  Inserting SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success
16:848  0:015   CPUBase=0 and ApicCPUBase=1 ApicCPUNum=8

See?

Yes, it was the change in Clover. "If there is a drop a one table then DropOEM set to false"

I will propose you to check once more, what tables you want to drop.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...