Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,866 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted

 

By the way a stupid question,how UEFI boot clover Yosemite USB installer pen drive works?How UEFI can find CLOVERX64.EFI on HFS+ Yosemite USB installer cause UEFI only support FAT32?

 

 

Because CloverX64.efi loads an HFS+ driver for using by UEFI from the folder /EFI/CLOVER/drivers64UEFI/

Link to comment
Share on other sites
Ingwar77
Ingwar77
Posted
Posted

.... You say iMessages went inactive; has it come back since you downgraded or is it still giving you the 'call Apple Support' spiel?

Yes, in my case iMessage / FaceTime become inactive, are invited to contact the support, with the same codes.

It is unclear why the reinstallation of Clover on the same computer with the same config resulted in a deactivation iMessage/FaceTime 

Link to comment
Share on other sites
FrDakota
FrDakota
Posted
Posted

There is something weird with since Clover r2953, I can no longer automatically reboot to the OS I used at last startup.

 

It reverts to the first of the list which is Mavericks in my case, I have to move to Yosemite (or Windows) to launch the good OS.

 

The Startup pane correctly sets the volume to reboot to. But once I change it to launch another OS Clover seems to set it on the first item in the list.

 

So if I want to default to Windows I have to start an OS X and set it with the Startup pane.

 

Reverting to Clover r2795 fixes the problem.

 

I'm using of course the motherboard's NVRAM not the nvram.plist (and the nvram UEFI driver is not installed).

Link to comment
Share on other sites
teeodor
teeodor
Posted
Posted

 

 

@teeodor

very unusual that your GPT/GUID disk does not have an ESP (EFI system partition). I would use gpt to add one:

Note: you probably need to boot from another disk to make changes to the partition table. 

this command will add an EFI type partition (if there is space). unmount every partition and run:

sudo gpt add -s 409600 -t C12A7328-F81F-11D2-BA4B-00A0C93EC93B disk0

this is a dual boot GUID disk example. your EFI will not be 1st partition but thats ok.

 

 

$ diskutil list disk0

/dev/disk0

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *750.2 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                  Apple_HFS OSX-                    697.7 GB   disk0s2

   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

   4:       Microsoft Basic Data C                       51.5 GB    disk0s4

 

$ sudo gpt -r show disk0

       start        size  index  contents

           0           1         PMBR

           1           1         Pri GPT header

           2          32         Pri GPT table

          34           6         

          40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

      409640  1362786480      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

  1363196120     1269544      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

  1364465664   100681728      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  1465147392        1743         

  1465149135          32         Sec GPT table

  1465149167           1         Sec GPT header

I did doall,after i format sudo mount_msdos /dev/disk0s4 /Volumes/EFI and after i install clover with this option.

But in the bios i don't see the efi partition and the system boot with chamaleon

post-856330-0-89223400-1414350084_thumb.png

Link to comment
Share on other sites
AsusFreak
AsusFreak
Posted
Posted

Has anyone had success installing Clover UEFI to a OS X software raid array. When I install Clover UEFI to the array called "RAID-0", it says it successfully completed yet but it puts the EFI folder in the root of the array "RAID-0", not in the EFI partition. I can mount the EFI partition on one of the raid drives and copy the EFI folder to it and it boots fine. But when you run the installer again to do an update it again writes to root, not EFI..

 

Thanks-

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

@fusion71au - i agree with you on this topic. consistency is very important.

 

I am concerned and interested in learning  how to properly specify MLB and ROM (if the RtVariable method is going away?) in the config.plist. Currently I use RtVariables to inject these 2 vars - but I have read that this is a deprecated method. So is there a best practice or method to keep the same value set?

 

That is, how to convert from RtVariables MLB and ROM method to SMBIOS variables? which SMBIOS are required?

 

SmUUID  - this seems to be the key to contain the ROM value in last 12 chars?

BoardSerialNumber - i believe this should be set to the MLB value?

 

 

@tluck,

 

What you've posted is indeed correct.  If MLB and ROM are not specified in the Rt Variables section, then by default, Clover will use the Main Board Serial Number in SMBIOS for the MLB value and the last 12 characters (6 bytes) of the SmUUID as the ROM value - see @dmazars' post on Clover r978.

 

IMHO, the Clover wiki is misleading when it says that MLB and ROM injection from Rt Variables is deprecated.  It was probably written when Apple was more lax about the actual values used for MLB and ROM ie in the past, any random value for MLB and ROM would work to activate iMessage/Facetime as long as the strings were the correct length and a credit card was attached to a user's AppleID---> Clover's defaults worked well and there was no need to manually specify values.

 

Now that they are checking for registered MLB/ROM values during activation (from genuine Macs or by calling Apple to register fake serials), it is more important than ever for the user to be able to specify those values in the config.plist.  It is up to Slice and the Clover developers as to the way they would like to do this but I see no reason to change the current method in Rt Variables....

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

@tluck,

 

What you've posted is indeed correct.  If MLB and ROM are not specified in the Rt Variables section, then by default, Clover will use the Main Board Serial Number in SMBIOS for the MLB value and the last 12 characters (6 bytes) of the SmUUID as the ROM value - see @dmazars' post on Clover r978.

 

IMHO, the Clover wiki is misleading when it says that MLB and ROM injection from Rt Variables is deprecated.  It was probably written when Apple was more lax about the actual values used for MLB and ROM ie in the past, any random value for MLB and ROM would work to activate iMessage/Facetime as long as the strings were the correct length and a credit card was attached to a user's AppleID---> Clover's defaults worked well and there was no need to manually specify values.

 

Now that they are checking for registered MLB/ROM values during activation (from genuine Macs or by calling Apple to register fake serials), it is more important than ever for the user to be able to specify those values in the config.plist.  It is up to Slice and the Clover developers as to the way they would like to do this but I see no reason to change the current method in Rt Variables....

You are quite right and AFAIK RtVariables are still working. We are not going to change current method.

One of the possible reason to change behavior is working NVRAM for those who have it not working before. Exclude EmuVariable and live in new conditions. I will not return to bad version.

  • Like 3
Link to comment
Share on other sites
FrDakota
FrDakota
Posted
Posted

DefaultVolume=LastBootedVolume?

 

It worked thanks.

 

So that means that the key DefaultVolume wasn't working correctly with previous versions of Clover ?

 

Because I always had that key, but set to Mavericks and I had the ability of remembering the last booted OS with Clover r2795.

Link to comment
Share on other sites
Marius_rg
Marius_rg
Posted
Posted

Not sure what happened, but since recently I cannot set in clover the Default boot volume. I tried with GUID and Vol Name, but without success. 

I'm using the latest clover 2976:

- 64Drivers: CsmVideoDxe-64.efi, FSInject-64.efi, HFSPlus.efi, NTFS.efi, OsxAptioFixDrv-64.efi, OsxFatBinaryDrv-64.efi

 

Attached the config.plist and clover bootlog.

 

Also, it's normal for clover to stay like 5s before the correct CSM resolution is set:

 

===

0:783  0:176    0 640x480 attr=3BF - ok, 640x480, working, highest, pref=0

0:784  0:001    1 800x600 attr=3BF - ok, 800x600, working, highest, pref=1
0:786  0:001    2 1024x768 attr=3BF - ok, 1024x768, working, highest, pref=2
0:787  0:001    3 1280x1024 attr=3BF - ok
0:794  0:007    4 1600x1200 attr=3BF - ok
0:796  0:001    5 1920x1200 attr=3BF - ok
0:797  0:001    6 1280x800 attr=3BF - ok
0:797  0:000  CsmVideo: New mode: 2 1024x768 - set
0:957  0:159   - SetMode pref 2 (2) = Success
0:957  0:000  CsmVideoCheckForVbe - Success
0:957  0:000  CsmVideoDriverBindingStart end Success
1:066  0:108  CsmVideo: New mode: 1 800x600 - blocking that switch
5:096  4:029  LoadDrivers() end
5:096  0:000  SetScreenResolution: 1920x1200 - setting Mode 5
5:096  0:000  CsmVideo: New mode: 5 1920x1200 - set
5:444  0:348  Video mode change to mode #5: Success
====

bootlog.log.txt

config.pdf

Link to comment
Share on other sites
TimeWalker75a
TimeWalker75a
Posted
Posted

 

Not sure what happened, but since recently I cannot set in clover the Default boot volume. I tried with GUID and Vol Name, but without success. 

I'm using the latest clover 2976:

Would you mind reading at least previous page of this thread before posting new question that has literally been answered 3 posts ago ? 

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

 

 

I'm using the latest clover 2976:

- 64Drivers: CsmVideoDxe-64.efi, FSInject-64.efi, HFSPlus.efi, NTFS.efi, OsxAptioFixDrv-64.efi, OsxFatBinaryDrv-64.efi

 

Attached the config.plist and clover bootlog.

 

Also, it's normal for clover to stay like 5s before the correct CSM resolution is set:

 

===

 

0:957  0:000  CsmVideoDriverBindingStart end Success
1:066  0:108  CsmVideo: New mode: 1 800x600 - blocking that switch
5:096  4:029  LoadDrivers() end
 
====

 

This is not normal. I may propose you to exclude other drivers from the folder drivers64UEFi to see who cause the delay.

Link to comment
Share on other sites
tluck
tluck
Posted
Posted

@slice and @fusion71au.

thank you. good news. I prefer the direct method for MLB and ROM by the RtVariables in config.plist.  And no, EmuVariable.efi is NOT being used anymore on the T420 platforms!  

 

@teeodor - does your GPT disk have MBR or PBMR.  sometimes this causes problems. run: sudo gpt -r show disk0

 

$ sudo gpt -r show disk1

       start        size  index  contents

           0           1         PMBR

           1           1         Pri GPT header

           2          32         Pri GPT table

...

 

$ sudo gpt -r show disk3

gpt show: disk3: Suspicious MBR at sector 0

       start        size  index  contents

           0           1         MBR

           1           1         Pri GPT header

Link to comment
Share on other sites
teeodor
teeodor
Posted
Posted

@slice and @fusion71au.

thank you. good news. I prefer the direct method for MLB and ROM by the RtVariables in config.plist.  And no, EmuVariable.efi is NOT being used anymore on the T420 platforms!  

 

@teeodor - does your GPT disk have MBR or PBMR.  sometimes this causes problems. run: sudo gpt -r show disk0

 

$ sudo gpt -r show disk1

       start        size  index  contents

           0           1         PMBR

           1           1         Pri GPT header

           2          32         Pri GPT table

...

 

$ sudo gpt -r show disk3

gpt show: disk3: Suspicious MBR at sector 0

       start        size  index  contents

           0           1         MBR

           1           1         Pri GPT header

pmbr

      start       size  index  contents

          0          1         PMBR

          1          1         Pri GPT header

          2         32         Pri GPT table

         34     409600      4  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

     409634          6         

     409640  194402768      1  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

  194812408    1269536      2  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

  196081944  780429040      3  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

  976510984     262151         

  976773135         32         Sec GPT table

  976773167          1         Sec GPT header

Link to comment
Share on other sites
anibalin
anibalin
Posted
Posted

Hi guys, I have this Asus P9X79 PRO (bios 4801 untouched) with a brand new hdd with 10.10 on it. Installed clover as uefi but get this nasty error on boot:

KDhHHcq.jpg

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>DropOEM_DSM</key>
			<false/>
			<key>Fixes</key>
			<dict>
				<key>AddDTGP_0001</key>
				<true/>
				<key>AddHDMI_8000000</key>
				<true/>
				<key>AddIMEI_80000</key>
				<true/>
				<key>AddPNLF_1000000</key>
				<true/>
				<key>DeleteUnused_400000</key>
				<true/>
				<key>FIX_ACST_4000000</key>
				<true/>
				<key>FIX_ADP1_800000</key>
				<true/>
				<key>FIX_RTC_20000</key>
				<true/>
				<key>FIX_S3D_2000000</key>
				<true/>
				<key>FakeLPC_0020</key>
				<true/>
				<key>FixAirport_4000</key>
				<true/>
				<key>FixDisplay_0100</key>
				<true/>
				<key>FixFirewire_0800</key>
				<true/>
				<key>FixHDA_8000</key>
				<true/>
				<key>FixHPET_0010</key>
				<true/>
				<key>FixIPIC_0040</key>
				<true/>
				<key>FixLAN_2000</key>
				<true/>
				<key>FixRegions_10000000</key>
				<true/>
				<key>FixShutdown_0004</key>
				<true/>
				<key>NewWay_80000000</key>
				<true/>
			</dict>
			<key>Name</key>
			<string>DSDT.aml</string>
			<key>ReuseFFFF</key>
			<false/>
		</dict>
		<key>DropTables</key>
		<array>
			<dict>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>Cpu0Ist</string>
			</dict>
			<dict>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>CpuPm</string>
			</dict>
			<dict>
				<key>Signature</key>
				<string>DMAR</string>
			</dict>
		</array>
		<key>HaltEnabler</key>
		<true/>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<false/>
			<key>EnableC6</key>
			<true/>
			<key>Generate</key>
			<dict>
				<key>CStates</key>
				<true/>
				<key>PStates</key>
				<true/>
			</dict>
		</dict>
	</dict>
	<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>npci=0x2000 kext-dev-mode=1</string>
		<key>DefaultVolume</key>
		<string>mati240</string>
		<key>Legacy</key>
		<string>PBR</string>
		<key>Log</key>
		<false/>
		<key>Secure</key>
		<false/>
		<key>Timeout</key>
		<integer>3</integer>
		<key>XMPDetection</key>
		<false/>
	</dict>
	<key>Devices</key>
	<dict>
		<key>Audio</key>
		<dict>
			<key>Inject</key>
			<string>No</string>
		</dict>
		<key>FakeID</key>
		<dict>
			<key>ATI</key>
			<string>0x0</string>
			<key>IMEI</key>
			<string>0x0</string>
			<key>IntelGFX</key>
			<string>0x0</string>
			<key>LAN</key>
			<string>0x0</string>
			<key>NVidia</key>
			<string>0x0</string>
			<key>SATA</key>
			<string>0x0</string>
			<key>WIFI</key>
			<string>0x0</string>
			<key>XHCI</key>
			<string>0x0</string>
		</dict>
		<key>USB</key>
		<dict>
			<key>AddClockID</key>
			<true/>
			<key>FixOwnership</key>
			<true/>
			<key>Inject</key>
			<true/>
		</dict>
	</dict>
	<key>DisableDrivers</key>
	<array>
		<string>Nothing</string>
	</array>
	<key>GUI</key>
	<dict>
		<key>Hide</key>
		<array>
			<string>BOOTX64.EFI</string>
			<string>Windows</string>
		</array>
		<key>Language</key>
		<string>en:0</string>
		<key>Mouse</key>
		<dict>
			<key>Enabled</key>
			<true/>
			<key>Mirror</key>
			<false/>
			<key>Speed</key>
			<integer>8</integer>
		</dict>
		<key>Scan</key>
		<dict>
			<key>Entries</key>
			<true/>
			<key>Legacy</key>
			<true/>
			<key>Tool</key>
			<true/>
		</dict>
		<key>Theme</key>
		<string>bootcamp</string>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleRTC</key>
		<true/>
		<key>AsusAICPUPM</key>
		<true/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>TRIM Enabler</string>
				<key>Find</key>
				<data>
				AEFQUExFIFNTRAA=
				</data>
				<key>Name</key>
				<string>IOAHCIBlockStorage</string>
				<key>Replace</key>
				<data>
				AAAAAAAAAAAAAAA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>External icons patch</string>
				<key>Find</key>
				<data>
				RXh0ZXJuYWw=
				</data>
				<key>Name</key>
				<string>AppleAHCIPort</string>
				<key>Replace</key>
				<data>
				SW50ZXJuYWw=
				</data>
			</dict>
		</array>
	</dict>
	<key>SMBIOS</key>
	<dict>
		<key>Trust</key>
		<false/>
	</dict>
	<key>SystemParameters</key>
	<dict>
		<key>InjectKexts</key>
		<string>Detect</string>
		<key>InjectSystemID</key>
		<true/>
	</dict>
</dict>
</plist>

OsxAptioFixDrv-64.efi its on drivers64UEFI

 

Thanks in advance. 

Link to comment
Share on other sites
doof
doof
Posted
Posted

Read through the thread but I didn't see the solution. v2981 built with Clover grower pro no longer shows the name of the boot volume. Worked correctly in earlier builds. Is this a bug or do I need to change something to get the volume name to show up?

Link to comment
Share on other sites
davidcmc
davidcmc
Posted
Posted

Read through the thread but I didn't see the solution. v2981 built with Clover grower pro no longer shows the name of the boot volume. Worked correctly in earlier builds. Is this a bug or do I need to change something to get the volume name to show up?

I have this same problem. I've downloaded r2976 and this problem began.

 

I've had to go back to r2953 to fix the issue.

 

r2976 shows a "Boot Mac OS X on ?" when I choose the OS X installation partition.

r2953, on the other hand, shows "Boot Mac OS X on OS X" ("OS X" is the partition name where Yosemite is installed).

Link to comment
Share on other sites
lexone
lexone
Posted
Posted

@powermapler, if you are using Clover in native UEFI mode, then you may try this:

- set Clover option as first one in boot order in UEFI/BIOS screen

- set your legacy windows drive as second one in boot order in UEFI/BIOS screen

- set Boot/Legacy=LegacyBiosDefault in Clover's config.plist

 

And then selecting any legacy entry in your Clover main menu should boot your legacy windows.

hey - so this does work for me to an extent...when I select my legacy Windows drive, it shows Windows loading and as soon as it's loading the login window I get no output to my monitors.  Any ideas?

Link to comment
Share on other sites
jamiethemorris
jamiethemorris
Posted
Posted

hey - so this does work for me to an extent...when I select my legacy Windows drive, it shows Windows loading and as soon as it's loading the login window I get no output to my monitors.  Any ideas?

Have you also tried PBR and PBRTest?

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