Clover General discussion

naiclub · February 13, 2015

clover 3178 boot does not boot up fails. :hysterical:

FranticJohny · February 13, 2015

I just discovered that I cannot boot in safe mode with OsxAptioFix2Drv-64.efi. With OsxAptioFixDrv-64.efi it works fine. Tried different slide values (0,8,100) but no luck.

blackosx · February 13, 2015

Oh, sorry. Up to monday I have no legacy computer. Now I am at system #1 having real NVRAM.

np.

I've run some tests and can confirm there is no problem when testing local builds.

r3177

1:667  0:205  Loading nvram.plist from Vol 'MainSystem' - loaded, size=597
1:669  0:001  PutNvramPlistToRtVars ...

r3168 I tested earlier was package from SF. Not sure why I get the problem with that.

clover 3178 boot does not boot up fails.

I can confirm r3178 does not get to GUI. It stalls with _ at top left corner of black screen before GUI.

wern apfel · February 13, 2015

I am very sorry for remind you about instructions exists #48

I've followed your instructions, and the error is gone, but i can't boot without cache, if i choose boot without cache it's booting normaly

I also tried it with Lion from external USB drive where i see the running dots, but the patch it's not working

<dict>
				<key>InfoPlistPatch</key>
                                <true/>
                                <key>Name</key>
                                <string>AppleSDXC</string>
                                <key>Find</key>
				<data>
				cGNpMTRlNCwxNmJj
				</data>
				<key>Replace</key>
				<data>
				cGNpMTIxNyw4MjIx
				</data>
			</dict>

Slice · February 14, 2015

np.

I've run some tests and can confirm there is no problem when testing local builds.

r3177
1:667  0:205  Loading nvram.plist from Vol 'MainSystem' - loaded, size=597
1:669  0:001  PutNvramPlistToRtVars ...
r3168 I tested earlier was package from SF. Not sure why I get the problem with that.

I can confirm r3178 does not get to GUI. It stalls with _ at top left corner of black screen before GUI.

Sorry, NULL pointer dereferencing. Corrected in 3180

blackosx · February 14, 2015

Thanks Slice

~~EDIT: r3180 still doesn't get to GUI for me. Last build that works here is r3177.~~

EDIT2: doh! I had a USB stick connected. Sorry for the misinformation.

r3181 fails compiling here with undeclared Macmini51,

Latest commit: Line #224 in /edk2/Clover/rEFIt_UEFI/Platform/gma.c

- case Macmini51:

+ case MacMini51:

r3181 booting fine.

AkimoA · February 14, 2015

got a Question regarding Legacy Boot Speed (Yosemite), Bios to Clover GUI on old GA-G33M-DS2R

it bothers me for a while now did a lot research to it and couldn´t find anything similar,

config.plist is very well adjusted

no Debug/Log enabled and wasn´t changed in between the Clover Updates (nor any other changes )

in r2967 i had the best success so far , Bios to Clover GUI in 5 seconds ( was quite acceptable for legacy boot)

than i did quite a big jump in revs to like 3094 from here on out until now (3168) im back to long waiting time from Bios to Clover GUI 25 -30 seconds

i did try boot7 made no difference with that ...

for me it seems that a kind of Timeout ( not talking about Boot Timeout within Clover ) was added to MBR Boot after 2967 ?

( also gave AppleHFS Drivers a shot which i guess was useless since the efi gets loaded later )

and nothing suspicious in the log either

any ideas

alexanderq · February 14, 2015

What is your boot.log says about that?

naiclub · February 14, 2015

hello Silce Why do I Compile. like this? Clover_v2k_r3182/3183.pkg<<<<

0:100 0:100 MemLog inited, TSC freq: 3392140641

0:100 0:000

0:100 0:000 Now is 14.2.2015, 23:43:45 (GMT+2047)

0:100 0:000 Starting Clover rev 3182:3183 on American Megatrends EFI

0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,35D60090-2276-45C3-ADC0-26A072C67ABF,0x28,0x64000) @8FC2D198

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 = 2200MHz

0:100 0:000 SmbiosTable.Type17->Size = 8192MB

0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 0 ChannelA-DIMM0

0:100 0:000 Type 17 Index = 1

droples · February 14, 2015

Clover3183

https://dl.dropboxusercontent.com/u/56771347/Clover3183.jpg

0:100  0:100  MemLog inited, TSC freq: 3403352453
0:100  0:000  
0:100  0:000  Now is 14.2.2015,  17:39:43 (GMT+2047)
0:100  0:000  Starting Clover rev 3183 on American Megatrends EFI
0:100  0:000  SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,0863F066-65A6-46F9-B747-72F25E463E02,0x28,0x64000) @DB846C18
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 = 1600MHz
0:100  0:000  SmbiosTable.Type17->Size = 8192MB

naiclub · February 14, 2015

Clover3183

https://dl.dropboxusercontent.com/u/56771347/Clover3183.jpg

0:100  0:100  MemLog inited, TSC freq: 3403352453
0:100  0:000  
0:100  0:000  Now is 14.2.2015,  17:39:43 (GMT+2047)
0:100  0:000  Starting Clover rev 3183 on American Megatrends EFI
0:100  0:000  SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,0863F066-65A6-46F9-B747-72F25E463E02,0x28,0x64000) @DB846C18
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 = 1600MHz
0:100  0:000  SmbiosTable.Type17->Size = 8192MB

Can you upload a the original file Your for me or not.?? thank

blackosx · February 15, 2015

Hi Slice

I notice I can choose to boot the embedded theme from config.plist but not from nvram.plist. Is this intentional or a bug?

Using: r3181

embedded theme in nvram.plist

1:698  0:001  PutNvramPlistToRtVars ...
1:698  0:000   Adding Key: Clover.Theme: Size = 8, Data: 65 6D 62 65 64 64 65 64 
1:698  0:000  theme embedded chosen from nvram is absent, get first theme
1:698  0:000  no default theme, get random theme theme.plist
1:699  0:000  Using theme 'hmf' (EFI\CLOVER\themes\hmf)
1:699  0:000  OS main and drive as badge
1:699  0:000  Font EFI\CLOVER\font\(null) is not loaded, using default
1:699  0:000  Choosing theme hmf

embedded theme in config.plist

0:991  0:000  Found theme directory: BGM
0:992  0:000  Found theme directory: BGM256
0:993  0:001  Found theme directory: black_green
0:993  0:000  Found theme directory: hmf
0:994  0:000  Found theme directory: ios7
0:995  0:000  Found theme directory: metal
0:996  0:000  Found theme directory: Minimalism Orange
0:996  0:000  Found theme directory: newyear
0:998  0:001  Found theme directory: red
0:999  0:000  Found theme directory: Simple Theme Light
1:000  0:000  Default theme: embedded
1:642  0:000  no themes available, using embedded
1:642  0:000  Choosing theme <null string>

Slice · February 15, 2015

Hi Slice

I notice I can choose to boot the embedded theme from config.plist but not from nvram.plist. Is this intentional or a bug?

Using: r3181

embedded theme in nvram.plist

1:698  0:001  PutNvramPlistToRtVars ...
1:698  0:000   Adding Key: Clover.Theme: Size = 8, Data: 65 6D 62 65 64 64 65 64 
1:698  0:000  theme embedded chosen from nvram is absent, get first theme
1:698  0:000  no default theme, get random theme theme.plist
1:699  0:000  Using theme 'hmf' (EFI\CLOVER\themes\hmf)
1:699  0:000  OS main and drive as badge
1:699  0:000  Font EFI\CLOVER\font\(null) is not loaded, using default
1:699  0:000  Choosing theme hmf

embedded theme in config.plist

0:991  0:000  Found theme directory: BGM
0:992  0:000  Found theme directory: BGM256
0:993  0:001  Found theme directory: black_green
0:993  0:000  Found theme directory: hmf
0:994  0:000  Found theme directory: ios7
0:995  0:000  Found theme directory: metal
0:996  0:000  Found theme directory: Minimalism Orange
0:996  0:000  Found theme directory: newyear
0:998  0:001  Found theme directory: red
0:999  0:000  Found theme directory: Simple Theme Light
1:000  0:000  Default theme: embedded
1:642  0:000  no themes available, using embedded
1:642  0:000  Choosing theme <null string>

This is a bug. I will study it tomorrow. Weekend now.

VirusX · February 15, 2015

hi guys,

since I updated from Clover 2976 to 3128, Clover "scan entries" for 30 seconds before the boot menu is loaded. I haven't changed anything in my config file. Is there a new option I have to deactivate?

Thanks

hi again,

I just wanted to report back that this issue got way better with the new 3168 version. It's down to ~5-10 seconds now. (I have to stop the time next time to get a exact time).

I haven't changed anything in my config - so whatever you were doing - thanks!

Zenith432 · February 15, 2015

I haven't changed anything in my config - so whatever you were doing - thanks!

Took out the busy wait loops.

Literally.

It's either 3157 if using AHCI, or 3164 if using IDE.

VirusX · February 15, 2015

Took out the busy wait loops.

Literally.

It's either 3157 if using AHCI, or 3164 if using IDE.

cool. The last version I used where the wait time still was high, was version 3156. I'm using AHCI - so yeah, that must be it

liujianwei · February 15, 2015

Is it a question that answered here? #46

Have tried several times,find that it's impossible to install EFI windows to GPT and MBR partition scheme on legacy BIOS based PC use legacy clover.Because SATA is inseparable,Microsoft won't let EFI windows install to MBR and Legacy BIOS PC's GPT by limitation.And clover also not friendly for legacy BIOS based PC because clover is pure EFI that cannot USB clover cannot boot MBR windows.

So my method is unplug SSD SATA cable and insall MBR windows to HDD,then plug back and boot clover to MBR windows.But I cannot activate windows by using SLIC.aml,so I use DAZ loader.

By the way,how to backup my bootable Yosemite installer with clover installed to DMG so that I can send to another people on internet to let him 1:1 copy use Win32DiskImager and boot it to install Yosemite?

Zenith432 · February 15, 2015

It's not impossible - I have it set up that way. It's difficult because Microsoft's tools for setting it up are 'braindead'.

You need two files on the Windows system partition.
\EFI\Microsoft\Boot\bootmgfw.efi
\EFI\Microsoft\Boot\BCD

the first is the Windows efi bootloader which is on the install DVD or somewhere in the Windows folder.

The 2nd is boot configuration database. Normal M$ tool to construct it is called BCDBOOT. On Windows 8, this tool let's you cross-construct an EFI-suitable BCD from a legacy-booted Windows. On Windows 7, it doesn't. It only constructs BCD for the type of Windows you have booted. So you can construct manually with BCDEDIT.

This is what a BCD for legacy Windows boot looks like.

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=<some-drive-letter>:
path                    \bootmgr
description             Windows Boot Manager
locale                  <some-locale>
default                 {default}
displayorder            {default}
timeout                 <some-timeout>

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=<some-drive-letter>:
path                    \Windows\system32\winload.exe
description             <some-Windows>
locale                  <some-locale>
osdevice                partition=<some-drive-letter>:
systemroot              \Windows

This is what a BCD for EFI Windows boot looks like.

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=<some-drive-letter>:
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  <some-locale>
default                 {default}
displayorder            {default}
timeout                 <some-timeout>

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=<some-drive-letter>:
path                    \Windows\System32\winload.efi
description             <some-Windows>
locale                  <some-locale>
osdevice                partition=<some-drive-letter>:
systemroot              \Windows

See the difference?

You can't load SLIC.aml from Clover if you chain-boot Windows in Legacy, because Clover doesn't patch ACPI tables in this sequence. DAZ boot loader (AKA grub4dos) patches ACPI tables to install SLIC.aml. If you chain-boot Windows in EFI mode, Clover patches ACPI tables and loads SLIC.aml.

Have tried several times,find that it's impossible to install EFI windows to GPT and MBR partition scheme on legacy BIOS based PC use legacy clover.Because SATA is inseparable,Microsoft won't let EFI windows install to MBR and Legacy BIOS PC's GPT by limitation.And clover also not friendly for legacy BIOS based PC because clover is pure EFI that cannot USB clover cannot boot MBR windows.
So my method is unplug SSD SATA cable and insall MBR windows to HDD,then plug back and boot clover to MBR windows.But I cannot activate windows by using SLIC.aml,so I use DAZ loader.

Slice · February 16, 2015

2558-02-15 :00.02.16.png

hello Silce Why do I Compile. like this? Clover_v2k_r3182/3183.pkg

0:100 0:100 MemLog inited, TSC freq: 3392140641

0:100 0:000

0:100 0:000 Now is 14.2.2015, 23:43:45 (GMT+2047)

0:100 0:000 Starting Clover rev 3182:3183 on American Megatrends EFI

0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,35D60090-2276-45C3-ADC0-26A072C67ABF,0x28,0x64000) @8FC2D198

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 = 2200MHz

0:100 0:000 SmbiosTable.Type17->Size = 8192MB

0:100 0:000 SmbiosTable.Type17->Bank/Device = BANK 0 ChannelA-DIMM0

0:100 0:000 Type 17 Index = 1

You can not. First value is revision updated, second value is committed.

So this line "Clover rev 3182:3183" can be only at developer with committing ability.

Hi Slice

I notice I can choose to boot the embedded theme from config.plist but not from nvram.plist. Is this intentional or a bug?

Hey blackosx,

How can you set embedded theme in nvram.plist?

blackosx · February 16, 2015

Hey blackosx,

How can you set embedded theme in nvram.plist?

Legacy boot combined with launch daemon and rc scripts installed.

sudo nvram Clover.Theme=embedded

reboot.

Scenario:

If user no longer has rc scripts running, but has an nvram.plist with theme entry then Clover will attempt to load that theme. Under normal circumstances this will not happen but it could and then user will not know why theme loaded is different to that set in config.plist, unless they read the bootlog. I found an nvram.plist on a Recovery HD which Clover was loading.

Slice · February 16, 2015

Rev.3184 lets you to set "embedded" and "random" themes from Clover prefPane.

To do this you have to make folders .../themes/embedded and .../themes/random as it done in Clover repository.

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/CloverPackage/CloverV2/EFI/CLOVER/themes/

blackosx · February 16, 2015

Useful addition Slice, but can't you just add the embedded and random entries to the pref pane menu without needing a theme directory for each? Clover Theme Manager can also set embedded and random theme entries by this method, without theme directories (it's still beta at the moment though and a new version will be out soon).

Slice · February 16, 2015

Useful addition Slice, but can't you just add the embedded and random entries to the pref pane menu without needing a theme directory for each? Clover Theme Manager can also set embedded and random theme entries by this method, without theme directories (it's still beta at the moment though and a new version will be out soon).

screenshot.jpg

I can't modify pref panel because I don't know Objective-C.

If you can then do this!

PS. Anyway preview of embedded theme?

blackosx · February 16, 2015

I'm no good with Obj-C either.

But yeah, if you want a preview of the embedded theme in the pref pane then you're right that having a theme folder is the simplest way.

liujianwei · February 16, 2015

It's not impossible - I have it set up that way. It's difficult because Microsoft's tools for setting it up are 'braindead'.

You need two files on the Windows system partition.

\EFI\Microsoft\Boot\bootmgfw.efi

\EFI\Microsoft\Boot\BCD

the first is the Windows efi bootloader which is on the install DVD or somewhere in the Windows folder.

The 2nd is boot configuration database. Normal M$ tool to construct it is called BCDBOOT. On Windows 8, this tool let's you cross-construct an EFI-suitable BCD from a legacy-booted Windows. On Windows 7, it doesn't. It only constructs BCD for the type of Windows you have booted. So you can construct manually with BCDEDIT.

This is what a BCD for legacy Windows boot looks like.
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=<some-drive-letter>:
path                    \bootmgr
description             Windows Boot Manager
locale                  <some-locale>
default                 {default}
displayorder            {default}
timeout                 <some-timeout>

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=<some-drive-letter>:
path                    \Windows\system32\winload.exe
description             <some-Windows>
locale                  <some-locale>
osdevice                partition=<some-drive-letter>:
systemroot              \Windows
This is what a BCD for EFI Windows boot looks like.
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=<some-drive-letter>:
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  <some-locale>
default                 {default}
displayorder            {default}
timeout                 <some-timeout>

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=<some-drive-letter>:
path                    \Windows\System32\winload.efi
description             <some-Windows>
locale                  <some-locale>
osdevice                partition=<some-drive-letter>:
systemroot              \Windows
See the difference?

You can't load SLIC.aml from Clover if you chain-boot Windows in Legacy, because Clover doesn't patch ACPI tables in this sequence. DAZ boot loader (AKA grub4dos) patches ACPI tables to install SLIC.aml. If you chain-boot Windows in EFI mode, Clover patches ACPI tables and loads SLIC.aml.

Thank you so much for your detail reply,here is my EasyBCD output

There is one entry in the Windows bootloader.

Default: Windows 7
Timeout: 30 seconds
Boot Drive: C:\

Entry #1
Name: Windows 7
BCD ID: {current}
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe

I think I need choose ESC in BIOS to select SATA driver to boot to windows 7 or clover bootloader.

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites