Jump to content

Clover not "acting right"


20 posts in this topic

Recommended Posts

For the couple of days now I've been trying to modify the GUI at the boot screen to:

  1. Hide unused drives for booting
  2. rename the titles so "boot from" is no longer there
  3. insert a new theme
  4. raise the resolution of the GUI

So far all I have been able to accomplish is hiding my unused drives and get my resolution straight. I've tried everything I could think of from using the configurator to modifying the config file myself and I can't see anything I should be doing but the names never change and also the theme never changes. Also, the only way the resolution would change is when I disabled CSM in bios. Everything is installed UEFI.

 

Any help is HIGHLY appreciated!

 

 

 

Link to comment
Share on other sites

Post a boot.log please, we can't do much without it. A couple of tips that might help:

 

- The Clover Preference Panel is the preferred method to set the active theme. You may do so from the terminal as well with the command: sudo nvram Clover.Theme=theme_name

- Always use a proper plist editor like PlistEdit Pro, you may corrupt the plist with a regular text editor.

- To eliminate the "boot from" text you'll need to create custom entries and use "FullTitle" instead of just "Title" for each entry.

Link to comment
Share on other sites

I attached the boot log and config files. I've already replaced "Title" key with "FullTitle" with no luck. If you see anything else in there that I should clean up let me know. I do have this strange "Shutdown computer due to error" that keeps popping up as well even though it shuts down fine. It's just not at the top of my list. Thanks again

BootNConfig.zip

Link to comment
Share on other sites

There's something wrong with your config, not the one you attached but the one that Clover tries to load but fails cause of a bad plist:

0:100  0:000  Found Plist String = , parse XML in LoadOptions
0:100  0:000  Xml in load options is bad
0:105  0:005  Using OEM config.plist at path: EFI\CLOVER\config.plist
0:105  0:000  EFI\CLOVER\config.plist loaded: Success
The plist you uploaded is practically empty but the one read by Clover contains several custom options like:
0:156  0:000  Hiding entries with string bootmgr.efi
0:156  0:000  Hiding entries with string BOOTX64.efi
0:552  0:000  Config set ResetAddr=0x0
0:552  0:000  Config calc ResetVal=0x0
0:552  0:000  Config set ResetVal=0x0
0:552  0:000  Config set ChassisType=0xD
0:552  0:000  Config set QPI=65535MHz
0:552  0:000  Config set CpuFreq=3503MHz
0:552  0:000  Config set CpuType=704
0:552  0:000  Config set BusSpeed=100098kHz
0:552  0:000  Error: invalid CustomUUID '' - should be in the format XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

Try redoing the plist with a proper editor and report back with a boot.log and config.plist again please.

 
And the bad shutdown report is a KP stored in the NVRAM to show next boot. Delete the /nvram.plist manually, you shouldn't need it with a UEFI board.
0:571  0:004  Loading nvram.plist from Vol 'Yosemite' - loaded, size=7037
0:572  0:001  PutNvramPlistToRtVars ...
0:572  0:000   Adding Key: aapl,panic-info: Size = 4473, Data: . . . 
 

EDIT: your custom entries don't work either because you're setting the wrong GUID. The Yosemite GUID you typed corresponds to your Recovery partition, and because of the path definition then the entry just fails to produce anything:

 

0:573  0:000  Custom entry 0 FullTitle:"OS X Yosemite" Path:"\System\Library\CoreServices\boot.efi" Type:1 Flags:0x0 matching Volume:"0655DC24 . . ."

0:573  0:000      Checking volume "Yosemite" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,B9C39835 . . .
0:573  0:000      Checking volume "Recovery HD" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(3,GPT,0655DC24 . . .
 
EDIT2: there's definitely something wrong with your Clover setup:
 
0:567  0:000   9. Volume:
0:567  0:000    PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(3,GPT,0655DC24-. . . )
0:571  0:004  Loading nvram.plist from Vol 'Yosemite' - loaded, size=7037
0:573  0:000      Checking volume "Recovery HD" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(3,GPT,0655DC24-. . . )) … skipped because path does not exist
 
The same GUID corresponds to 2 different partitions??? This is weird… And Clover sees several themes at the beginning but then says there's no theme available and uses the embedded one :S:
0:108  0:003  Found theme applestyle
0:112  0:003  Found theme BGM
0:117  0:005  Found theme black_green
0:120  0:003  Found theme BLUEMAC
0:123  0:003  Found theme BOOTCAMP
0:125  0:002  Found theme christmas
0:127  0:002  Found theme ICLOVER
0:129  0:001  Found theme magnifico
0:132  0:003  Found theme METAL
0:136  0:003  Found theme MRENGLES
0:138  0:002  Found theme NEWYEAR
0:141  0:002  Found theme ORANGE
0:143  0:002  Found theme OS_BOX
0:145  0:002  Found theme OS_ONE
0:147  0:001  Found theme Shield
0:153  0:006  Found theme THINKPAD

0:573  0:000  no themes available, using embedded
0:573  0:000  Choosing theme <null string>

There might be a bigger problem here preventing Clover from reading your files properly. Try formatting the EFI partition as FAT32 and reinstalling Clover again. Before that save your config, ACPI tables and kexts and restore them after the installer is finished.

 

Link to comment
Share on other sites

ok only using clover configurator and just the items i need to boot without manually inputting flags this is what I was able to come up with. I have also tried to use custom names for the boot loader without success. I agree there is something severely weird going on here as the path being used by clover is the config.plist file that I am including in the zip. **I  have plist edit pro now**

 

EFI is fat32, where do I find the ACPI tables, and which kexts should I save?

 

by the way, where is nvram.plist?? I have searched all over looking for it...

BootNConfigpart2.zip

Link to comment
Share on other sites

This other config is complete but the log says there's an error:

0:100  0:000  Found Plist String = , parse XML in LoadOptions
0:100  0:000  Xml in load options is bad

According to the log, you don't seem to have custom DSDT or SSDT tables, nor kexts injected by Clover. I suggested that just in case you do have them somewhere and avoid losing them.

 

Something you could try before formatting and starting over is to add AppleHFS.efi to drivers64UEFI, just to make sure it's not a problem with the VBoxHFS one. And while you're at it delete the PartitionDxe-64.efi driver as well, you shouldn't need it.

 

The nvram.plist is hidden in the root partition of your OS, you can delete it with the terminal command: sudo rm /nvram.plist

Link to comment
Share on other sites

with configurator, I went as minimal as possible. I removed PartitionDxe-64.efi and tried a couple of different options with AppleHFS.efi. Basically, I tried just adding it and then tried with adding it and deleting VBoxHFS with the same results that I have been getting. What exactly does the xml in load options is bad mean?

 

something else that is weird is that when I search clover in Finder, it shows up with three different clover folders as well as 3 different install logs that say its was installed at 3 different times all within 5 mins of each other

 

getting rid of the nvram.plist didn't work for the shutdown error. The computer itself shuts down ok. The error only pops up at start up after logging in. The report says its a cpu kernal panic

Link to comment
Share on other sites

Backup your config.plist and try to get rid of every Clover folder you find, format the EFI partition as FAT32 and install Clover again. The kernel panic log should have disappeared after deleting the nvram.plist but it seems you'll need to get rid of the key instead:

 

sudo nvram -d aapl,panic-info
Next time upload a full DarwinDumper report please.
Link to comment
Share on other sites

That's a kernel panic sign, you most likely forgot to add some kext, ACPI table or preference on the config.plist to avoid it. To see more about the KP boot in verbose mode next time and try to take a picture or make a video cause it might show for just a second.

Link to comment
Share on other sites

I got everything up and running with a chimera bootloader. I reinstalled clover using this guide http://www.skylineosx.com/installation/switching-from-chameleonchimera-to-clover/

 

Then setup clover configurator like this http://www.skylineosx.com/installation/configuring-clover/

 

That pretty everything I did before and I keep get that panic. Took a video of it and it looks like a kernal 0x9

 

https://www.youtube.com/watch?v=PdmlQqro3MM&list=UUqttgNX7j-gPF3X6vGA61DQ

 

Clover is even using themes I never even loaded during install. Its driving me crazy so I'll be stopping for the night.

Link to comment
Share on other sites

I got clover straightened out enough to be able to boot from it. I formated the EFI drive and reinstalled Clover. Used configurator to compile the config.plist. Now it boots like before.

 

The problems I have are:


  • I don't have any audio devices showing up in system info even though I installed the drivers
  • The computer takes about 20 secs to shut off after OS X has shutdown
  • At startup after login, I get a "You shut down your computer because of a problem" error even though it shut down by itself. The report that follows shows a CPU 5 kernel panic,
  • Clover keeps using themes I never installed(Christmas, NewYear, Merglaian?) and rotates between them. Clover picks which one it wants to use

 

Everything else works great. Bluetooth, all USB ports, performance is nice. Just have annoyances I need some help with

 

Attached the Darwin Report

DarwinDumper_2.9.6_AMI_X64_3079_Yos_MePeep.zip

Link to comment
Share on other sites

1- You're using the automatic audio layout detection but it doesn't work all the time:

4:497  0:000  HDA Controller [8086:1E20] :: PciRoot(0x0)\Pci(0x1B,0x0) => codec not detected

Select the layout manually according to the patch you applied. If it's Toleda's method it could be 1, 2 or 3.

 

2- The delay is most likely caused by the EvOReboot kext. I don't think you need it with Clover. Other kexts I'm not sure you need are VoodooTSCSync, NullCPUPowerManagement and ACPISensors (this one might be inside /S/L/E/FakeSMC.kext/Contents/PlugIns).

 

3- You've still got the nvram.plist in the root partition:

0:545  0:007  Loading nvram.plist from Vol 'Yosemite' - loaded, size=6869
0:551  0:006  PutNvramPlistToRtVars ...
0:551  0:000   Skipping EmuVariableUefiPresent
0:551  0:000   Adding Key: LocationServicesEnabled: Size = 1, Data: 01 
0:551  0:000   Skipping OsxAptioFixDrv-RelocBase
0:551  0:000   Adding Key: aapl,panic-info

Delete the file once again, delete the key from the nvram and disable the script that generates the file at shutdown (which shouldn't save it as you supposedly have a working NVRAM):

sudo rm /nvram.plist
sudo nvram -d aapl,panic-info
sudo mv /etc/rc.shutdown.d/80.save_nvram_plist.local /etc/rc.shutdown.d/80.save_nvram_plist.local.disabled

4- Select the theme with the Clover PrefPane or in GUI/Theme on your config.plist, otherwise it will be selected randomly:

0:551  0:000  no default theme, get random theme theme.plist
0:553  0:001  Using theme 'MRENGLES' (EFI\CLOVER hemes\MRENGLES)
Link to comment
Share on other sites

  • 8 months later...
 Share

×
×
  • Create New...