Clover General discussion

[artur_pt]

hello Slice

 

without /efi/Acpi/

and config.plist in /efi

 

0:100  0:100  MemLog inited, TSC freq: 2261463320
0:100  0:000  LegacyRegion2: Chipset/proc: 0x00448086
0:100  0:000   Core i7 processors (PAM 0x40-0x47)
0:100  0:000   Test PAM1=(0x41=11, 0x5a=00, 0x81=09, 0x91=1D) at chipset 00448086
0:100  0:000  , Install = Success
0:122  0:022  BiosVideoDriverEntryPoint!
0:135  0:012  BiosVideoDriverBindingStart!
0:135  0:000  BiosVideoCheckForVbe
0:162  0:026   Edid1+
0:162  0:000   found Detail Timing 1366x768
0:162  0:000  timing string @0xFE:AUO

0:162  0:000  timing string @0xFE:B156XW02 V2
0:188  0:026   Edid0+
0:188  0:000   found Detail Timing 1366x768
0:188  0:000  ... already present
0:188  0:000  timing string @0xFE:AUO

0:188  0:000  timing string @0xFE:B156XW02 V2
0:192  0:003	 0 1152x864 attr=BA - ok, edid-
0:192  0:000	 1 1280x960 attr=BA - ok, edid-
0:192  0:000	 2 640x480 attr=BB - ok, edid-, 640x480, working, highest, pref=2
0:192  0:000	 3 800x600 attr=BB - ok, edid-, 800x600, working, highest, pref=3
0:192  0:000	 4 1024x768 attr=BB - ok, edid-, 1024x768, working, highest, pref=4
0:192  0:000	 5 1280x1024 attr=BA - ok, edid-
0:193  0:000	 6 1400x1050 attr=BA - ok, edid-
0:193  0:000	 7 1600x1200 attr=BA - ok, edid-
0:193  0:000	 8 1792x1344 attr=BA - ok, edid-
0:193  0:000	 9 1856x1392 attr=BA - ok, edid-
0:194  0:000    10 1920x1440 attr=BA - ok, edid-
0:194  0:000    11 1366x768 attr=BB - ok, edid+, working, highest, pref=11
0:194  0:000  BV new mode: 11 1366x768
0:737  0:543   SetMode pref 11 (11) = Success
0:737  0:000  BiosVideoDriverBindingStart - END: Success!
2:769  2:031 
2:769  0:000  Starting rEFIt rev 1120 on CLOVER EFI
2:769  0:000  SelfDevicePath=PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,A89AA4C5-55A4-4DB8-BBC4-1029F51288DE,0x64028,0x21C5E358) @9E864898
2:826  0:056  Theme: AppleStyle Path: EFI\BOOT\themes\AppleStyle
2:900  0:074  Total Memory Slots Count = 2
2:900  0:000  Type 17 Index = 0
2:900  0:000  SmbiosTable.Type17->Speed = 1067
2:900  0:000  SmbiosTable.Type17->Size = 4096
2:900  0:000  mTotalSystemMemory = 4096
2:900  0:000  Type 17 Index = 1
2:900  0:000  SmbiosTable.Type17->Speed = 1067
2:900  0:000  SmbiosTable.Type17->Size = 2048
2:900  0:000  mTotalSystemMemory = 6144
2:900  0:000  Boot status=0
2:900  0:000  Clover revision: 1120  running on EasyNote TM86
2:900  0:000  ... with board EasyNote TM86
2:907  0:007  ConfigPlistPath: EFI\config.plist
2:908  0:000  Oem config.plist not found at path: EFI\config.plist
2:909  0:001  Error loading config.plist! Status=Not Found

 

and don't read the info in /efi/oem/systemname

 

with /efi/acpi/

and config.plist in /efi

 

-------------------------------
DATE: 2013-02-16 TIME: 15:35:31
-------------------------------
0:100  0:100  MemLog inited, TSC freq: 2261466690
0:100  0:000  LegacyRegion2: Chipset/proc: 0x00448086
0:100  0:000   Core i7 processors (PAM 0x40-0x47)
0:100  0:000   Test PAM1=(0x41=11, 0x5a=00, 0x81=09, 0x91=1D) at chipset 00448086
0:100  0:000  , Install = Success
0:122  0:022  BiosVideoDriverEntryPoint!
0:135  0:012  BiosVideoDriverBindingStart!
0:135  0:000  BiosVideoCheckForVbe
0:162  0:026   Edid1+
0:162  0:000   found Detail Timing 1366x768
0:162  0:000  timing string @0xFE:AUO

0:162  0:000  timing string @0xFE:B156XW02 V2
0:188  0:026   Edid0+
0:188  0:000   found Detail Timing 1366x768
0:188  0:000  ... already present
0:188  0:000  timing string @0xFE:AUO

0:188  0:000  timing string @0xFE:B156XW02 V2
0:192  0:003	 0 1152x864 attr=BA - ok, edid-
0:192  0:000	 1 1280x960 attr=BA - ok, edid-
0:192  0:000	 2 640x480 attr=BB - ok, edid-, 640x480, working, highest, pref=2
0:192  0:000	 3 800x600 attr=BB - ok, edid-, 800x600, working, highest, pref=3
0:192  0:000	 4 1024x768 attr=BB - ok, edid-, 1024x768, working, highest, pref=4
0:192  0:000	 5 1280x1024 attr=BA - ok, edid-
0:193  0:000	 6 1400x1050 attr=BA - ok, edid-
0:193  0:000	 7 1600x1200 attr=BA - ok, edid-
0:193  0:000	 8 1792x1344 attr=BA - ok, edid-
0:193  0:000	 9 1856x1392 attr=BA - ok, edid-
0:194  0:000    10 1920x1440 attr=BA - ok, edid-
0:194  0:000    11 1366x768 attr=BB - ok, edid+, working, highest, pref=11
0:194  0:000  BV new mode: 11 1366x768
0:732  0:537   SetMode pref 11 (11) = Success
0:732  0:000  BiosVideoDriverBindingStart - END: Success!
2:724  1:992 
2:724  0:000  Starting rEFIt rev 1120 on CLOVER EFI
2:725  0:000  SelfDevicePath=PcieRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,A89AA4C5-55A4-4DB8-BBC4-1029F51288DE,0x64028,0x21C5E358) @9E864898
2:781  0:056  Theme: AppleStyle Path: EFI\BOOT\themes\AppleStyle
2:855  0:074  Total Memory Slots Count = 2
2:855  0:000  Type 17 Index = 0
2:855  0:000  SmbiosTable.Type17->Speed = 1067
2:855  0:000  SmbiosTable.Type17->Size = 4096
2:855  0:000  mTotalSystemMemory = 4096
2:855  0:000  Type 17 Index = 1
2:855  0:000  SmbiosTable.Type17->Speed = 1067
2:855  0:000  SmbiosTable.Type17->Size = 2048
2:855  0:000  mTotalSystemMemory = 6144
2:855  0:000  Boot status=0
2:855  0:000  Clover revision: 1120  running on EasyNote TM86
2:855  0:000  ... with board EasyNote TM86
2:862  0:007  ConfigPlistPath: EFI\config.plist
2:916  0:053  Using OEM config.plist at path: EFI\config.plist

 

last version 1112 working well with all in /efi/oem/systemname/acpi/

 

now i'm working in 1120 but all the info in /efi

 

good hack

[dmazar]

Hi, dmazar!

 

I think i found what's the issue that causes that stretched boot screen, at least for my Ion netbook: apparently, my correct resolution (1368x768), is not being detected, even with EDID injection, as you can see in my preboot.log: preboot.log.zip

 

Is there a workaround for this?

 

Im using this lines under Graphics in my config.plist:

 

 

<key>GraphicsInjector</key>

<string>Yes</string>

<key>PatchVBios</key>

<string>Yes</string>

<key>CustomEDID</key>

<string>a lots of numbers</string>

 

Best regards.

 

P.S.: I checked my EDID txt dump from DarwinDumper and found these lines:

 

 

Detailed mode: Clock 71.900 MHz, 270 mm x 150 mm

1366 1414 1480 1486 hborder 0

768 774 782 806 vborder 0

-hsync -vsync

 

So my monitor not only support the highest resolution possible with my Ion graphics: it supports even higher resolutions. I guess that means that either clover cannot read my EDID for some reason (i tried reinstalling clover a couple of times, btw) or there's something wrong with the patching of my Vbios.

Ok, there are two things needed to patch video bios:

1. unlocking video bios memory area for writing, because it is normally locked for writing after BIOS installs video bios driver to memory

2. patching resolutions table in video bios to enable your resolution

 

In your case it fails in point 1. above, because you have NVIDIA chipset, and we do not know how to unlock video bios area on that chipset.

0:100 0:000 LegacyRegion2: Chipset/proc: 0x0A8210DE
0:100 0:000 Unknown chipset
0:101 0:001 Test PAM1=(0x41=00, 0x5a=00, 0x81=00, 0x91=33) at chipset 0A8210DE
0:101 0:000 , Chipset not detected - exiting
...
8:054 0:000 VideoBiosPatchNativeFromEdid:
8:054 0:000 Bios: nVidia, nv_data_table_offset: 0x298, nv_data_table: 0xC029A, std_vesa: 0xC8014, nv_mode_table: 0xC8019, mode_table_size: 0x10
8:054 0:000 VideoBiosPatchInit(LegacyRegion = Not Found, LegacyRegion2 = Not Found) = Not Found
8:054 0:000 = not done.
...

This LegacyRegion2 protocol is the service that Clover uses for unlocking vbios, and your chipset is not supported.

[dmazar]

Hi, dmazar!

 

I think i found what's the issue that causes that stretched boot screen, at least for my Ion netbook: apparently, my correct resolution (1368x768), is not being detected, even with EDID injection, as you can see in my preboot.log: preboot.log.zip

 

Is there a workaround for this?

 

Im using this lines under Graphics in my config.plist:

 

 

<key>GraphicsInjector</key>

<string>Yes</string>

<key>PatchVBios</key>

<string>Yes</string>

<key>CustomEDID</key>

<string>a lots of numbers</string>

 

Best regards.

 

P.S.: I checked my EDID txt dump from DarwinDumper and found these lines:

 

 

Detailed mode: Clock 71.900 MHz, 270 mm x 150 mm

1366 1414 1480 1486 hborder 0

768 774 782 806 vborder 0

-hsync -vsync

 

So my monitor not only support the highest resolution possible with my Ion graphics: it supports even higher resolutions. I guess that means that either clover cannot read my EDID for some reason (i tried reinstalling clover a couple of times, btw) or there's something wrong with the patching of my Vbios.

Ok, there are two things needed to patch video bios:

1. unlocking video bios memory area for writing, because it is normally locked for writing after BIOS installs video bios driver to memory

2. patching resolutions table in video bios to enable your resolution

 

In your case it fails in point 1. above, because you have NVIDIA chipset, and we do not know how to unlock video bios area on that chipset.

0:100 0:000 LegacyRegion2: Chipset/proc: 0x0A8210DE
0:100 0:000 Unknown chipset
0:101 0:001 Test PAM1=(0x41=00, 0x5a=00, 0x81=00, 0x91=33) at chipset 0A8210DE
0:101 0:000 , Chipset not detected - exiting
...
8:054 0:000 VideoBiosPatchNativeFromEdid:
8:054 0:000 Bios: nVidia, nv_data_table_offset: 0x298, nv_data_table: 0xC029A, std_vesa: 0xC8014, nv_mode_table: 0xC8019, mode_table_size: 0x10
8:054 0:000 VideoBiosPatchInit(LegacyRegion = Not Found, LegacyRegion2 = Not Found) = Not Found
8:054 0:000 = not done.
...

This LegacyRegion2 protocol is the service that Clover uses for unlocking vbios, and your chipset is not supported.

[Slice]

@artur-pt

I understand your problem

2:900 0:000 Clover revision: 1120 running on EasyNote TM86
2:900 0:000 ... with board EasyNote TM86

Your board name contains a space and I am not sure it is properly translated into folder name, or, may be you named OEM folder with other invisible symbol.

it must be

/EFI/OEM/EasyNote TM86/

The space works in my case so globally it is not a problem

[Slice]

4all

New installer does not install themes and drivers by default. You have to explicitly choose them.

[tdtran1025]

Slice,

The instruction for installing on RAID0 volumes is ambiguous. How do I install to RAID0. Another thing, changing the theme sometimes does not occur after reboot. this feature is finicky. It does it whenever it feels like it, even though I deleted all other themes but the one I want to use.

BTW, I still legacy BIOS board. Everything works fine, if I can install it on RAID0 just for curiosity. I can boot the RAID0 volumes by using USB or another volume, however.

 

To further clarify, I can use USB or another Clover volume to boot my existing RAID0, which has Chameleon on helper Boot partitions.

If I understand correctly Magnifico's instruction, I would have to create 2 new EFI partitions on main RAID0 spanned volumes, isn't it?

Wouldn't this destroy the Chameleon function in helper partitions?

Thank you.

[magnifico]

Slice,

The instruction for installing on RAID0 volumes is ambiguous. How do I install to RAID0. Another thing, changing the theme sometimes does not occur after reboot. this feature is finicky. It does it whenever it feels like it, even though I deleted all other themes but the one I want to use.

BTW, I still legacy BIOS board. Everything works fine, if I can install it on RAID0 just for curiosity. I can boot the RAID0 volumes by using USB or another volume, however.

 

To further clarify, I can use USB or another Clover volume to boot my existing RAID0, which has Chameleon on helper Boot partitions.

If I understand correctly Magnifico's instruction, I would have to create 2 new EFI partitions on main RAID0 spanned volumes, isn't it?

Wouldn't this destroy the Chameleon function in helper partitions?

Thank you.

 

 

What is ambiguous? It is a unique facility

Trusted :wink2:

[artur_pt]

hello Slice

 

i'm testing...

 

but the tree is good , never have that problem... with folder names...

 

 

thanks

 

good hack

 

edit: same thing with rev 1126

 

i notice now to do something inside /EFI

 

always ask to give administrator permission

 

and before no...

 

boot_1112.txt

[Slice]

hello Slice

 

i'm testing...

 

but the tree is good , never have that problem... with folder names...

 

 

thanks

 

good hack

 

edit: same thing with rev 1126

 

i notice now to do something inside /EFI

 

always ask to give administrator permission

 

and before no...

 

boot_1112.txt

Lets think what is wrong.

Related codes are the follow

 DBG("  running on %a\n",   gSettings.OEMProduct);
 DBG("... with board %a\n", gSettings.OEMBoard);

 UnicodeSPrint(gSettings.ConfigName, 64, L"config");

 if (FileExists(SelfRootDir, PoolPrint(L"EFI\\OEM\\%a\\%s.plist", gSettings.OEMProduct, gSettings.ConfigName))) {
   OEMPath = PoolPrint(L"EFI\\OEM\\%a", gSettings.OEMProduct);
 }

As I see

Clover revision: 1120 running on EasyNote TM86

so we know that gSettings.OEMProduct = "EasyNote TM86"

Then it checks

If (FileExists...) with path /EFI/OEM/EasyNote TM86/config.plist

Where is the problem?

May be you use HFS+ formatted partition and forget to use HFSPlus driver?

Or it searches /EFI folder on other partition then you expected?

[supaJ]

Hi all,

 

I own a Dell Studio XPS 9100 and I can't get to boot Clover off a USB flash disk on this PC. I know the boot disk works because I have tried it o other computers. Immediately after the Bios Post screen, after Clover begins to load, I get a message on my screen saying the monitor does not support the current resolution. I have attempted to correct this in 'refit.conf' by setting 'screen_resolution' to my monitor's default - '1600x900'.

 

 

# Set desired screen resolution if enabled

screen_resolution 1600x900

 

But I still get the same unsupported resolution message on my screen. Can anybody help please? Thanks.

[PJALM©]

Slice, this is what i get from boot log for mine but can't figure out how to use the OEM folder, what folder name should it be.

 

0:104 0:000 Clover revision: 1135 running on System Product Name

0:104 0:000 ... with board MAXIMUS V GENE

[k3nny]

@PJALM:

Use "MAXIMUS V GENE", without the quotation marks of course.

[artur_pt]

hello Slice

 

the only problem is with rev 1112, and rev before u can see with boot.log all working...

 

after 1112 only works with the files inside EFI/Acpi/generate/ and EFI/config.plist

 

it ignores EFI/OEM/EasyNote TM86/Acpi/generate/

 

EFI/OEMEasyNote TM86/config.plist

 

i don't see why ??? but it works the way i tell /EFI/Acpi/

 

something change in code....

 

only thing notorius i change in config.plist is using custom edid, but i use with rev it already working..

 

good hack

[Slice]

hello Slice

 

the only problem is with rev 1112, and rev before u can see with boot.log all working...

 

after 1112 only works with the files inside EFI/Acpi/generate/ and EFI/config.plist

 

it ignores EFI/OEM/EasyNote TM86/Acpi/generate/

why "generate"? What is mean?

 

EFI/OEMEasyNote TM86/config.plist

where is / after OEM?

Are you sure all folders have correct names?

i don't see why ??? but it works the way i tell /EFI/Acpi/

 

something change in code....

 

only thing notorius i change in config.plist is using custom edid, but i use with rev it already working..

 

good hack

The codes wasn't changed. I shown you these three lines.

[magnifico]

New Theme By Magnifico

 

Your suggestions and criticisms are accepted by me

 

MagnificoTheme.zip

[artur_pt]

hello Slice

 

sorry wrong path i don't know where i get that...

 

what i mean to tell is

 

EFI/Acpi/patched/

 

 

and

 

 

it ignores EFI/OEM/EasyNote TM86/Acpi/patched/

 

 

 

EFI/OEM/EasyNote TM86/config.plist

 

 

anyway it works all versions but for me lasts versions ignores /EFI/OEM folder.

 

 

forget the issue... i will tell u if anything change next versions...

 

thanks with the nice work u are doing with Clover

 

good hack

 

hello mag

 

nice theme for the cat.. is a female ????

 

rsrsrs

 

good hack for u my friend

[Slice]

/Volumes/EFI/EFI/BOOT/CLOVERX64.efi

[theconnactic]

Sorry, i moved it to the general discussion topic to not to polute this topic, Slice. Anyway, i'm not sure i understand you: i already have this file inside /Volumes/EFI/EFI/BOOT/CLOVERX64.efi, along with some others (BOOTX64.efi, CLOVERIA32.efi and two refit files). Should i remove all others?

 

Best regards.

[theconnactic]

Hi, Slice, dmazar and all developers!

 

I followed your instructions to do UEFI boot with Clover (r 9xx). Since my board is a GA-H77-DS3H, i used the HFSPlus.efi (which i had to find elsewhere, since CloverGrower didn't install it for me and appears to not have the option in the customization menu) and OsxFatBinaryDrv-64.efi combination. When i try to boot from UEFI, with flags -v npci=0x2000 arch=x86_64 slide=0, i get these lines:

 

Error allocating 0x1d72 pages at 0x00000000009ea000 alloc type 2

Loading 'mach_kernel'...

.....Error allocating 0x535 pages at 0x0000000000200000 alloc type 2

Error loading kernel 'mach_kernel' (0x9)

 

Then it hangs.

 

What should i change?

 

I try removing the BOOTX64.efi installed by CloverGrower and rename CLOVERX64.efi to BOOTX64.efi, but the result is even worse: i lose the possibility of booting at all (OSX partition does not appear). Same if i use VBoxHFS.efi.

 

Should i move mach_kernel to the EFI partition? Should i have removed the Boot, Boot1 etc files and the EFI folder that's in the root of my OSX partition? (i left them alone because in case anything went wrong, like it went, i could aways boot from BIOS, which already works real nice for me). Perhaps, instead of copying the EFI folder and pasting it in the EFI partition, i should have only copied the contents of the EFI folder and put them there...? Any light on this subject would be much appreciated.

 

Best regards.

 

P.S.: where do i find the HFSPlus.efi file do you recommend? It's not inside CloverGrower (at least for me) and perhaps the one i used (as said before, i downloaded it elsewhere) is not the correct one (it's from an iMac 13,1).

[magnifico]

 

 

 

hello mag

 

nice theme for the cat.. is a female ????

 

rsrsrs

 

good hack for u my friend

 

No , Simoes is my panther

...rsrsrsrsrsrsr

[xpamamadeus]

Hi, Slice, dmazar and all developers!

 

I followed your instructions to do UEFI boot with Clover (r 9xx). Since my board is a GA-H77-DS3H, i used the HFSPlus.efi (which i had to find elsewhere, since CloverGrower didn't install it for me and appears to not have the option in the customization menu) and OsxFatBinaryDrv-64.efi combination. When i try to boot from UEFI, with flags -v npci=0x2000 arch=x86_64 slide=0, i get these lines:

 

Error allocating 0x1d72 pages at 0x00000000009ea000 alloc type 2

Loading 'mach_kernel'...

.....Error allocating 0x535 pages at 0x0000000000200000 alloc type 2

Error loading kernel 'mach_kernel' (0x9)

 

Then it hangs.

 

What should i change?

 

I try removing the BOOTX64.efi installed by CloverGrower and rename CLOVERX64.efi to BOOTX64.efi, but the result is even worse: i lose the possibility of booting at all (OSX partition does not appear). Same if i use VBoxHFS.efi.

 

Should i move mach_kernel to the EFI partition? Should i have removed the Boot, Boot1 etc files and the EFI folder that's in the root of my OSX partition? (i left them alone because in case anything went wrong, like it went, i could aways boot from BIOS, which already works real nice for me). Perhaps, instead of copying the EFI folder and pasting it in the EFI partition, i should have only copied the contents of the EFI folder and put them there...? Any light on this subject would be much appreciated.

 

Best regards.

 

P.S.: where do i find the HFSPlus.efi file do you recommend? It's not inside CloverGrower (at least for me) and perhaps the one i used (as said before, i downloaded it elsewhere) is not the correct one (it's from an iMac 13,1).

post names of all drivers u have in drivers64uefi folder

it looks as u dont have osxaptiofix or u have osxlowmem and u shouldnt have it.

[theconnactic]

post names of all drivers u have in drivers64uefi folder

 

Thank you for the answer! I have a GA-H77-DS3H, UEFI BIOS.

 

I left only two drivers inside the drivers64uefi folder: HFSPlus.efi and OsxFatBinaryDrv-64.efi

 

Best regards!

 

EDIT: i reinstalled it from scratch, re-run the CloverGrower command, yet the results are the same (with only HFSPlus.efi - this time i notice it is indeed provided in a different folder, "Files"- and OsxFatBinaryDrv-64.efi in Drivers64 UEFI). Gosh, i'm starting to wonder if Clover simply doesn't like the UEFI implementation of the H77 DS3H board, which would be extremely unlucky for me. In BIOS mode, everything works like a charm, though. Is there anything i didn't try that i should?

 

As a side note, my revision of Clover (988 - it seems that the command cannot download anything newer) has a little bug in the package builder: i select Customize and check specific driver boxes, only to find that when it installs, it installs all of them, so i had to remove them manually.

 

Best regards!

[dmazar]

I followed your instructions to do UEFI boot with Clover (r 9xx). Since my board is a GA-H77-DS3H, i used the HFSPlus.efi (which i had to find elsewhere, since CloverGrower didn't install it for me and appears to not have the option in the customization menu) and OsxFatBinaryDrv-64.efi combination. When i try to boot from UEFI, with flags -v npci=0x2000 arch=x86_64 slide=0, i get these lines:

 

Error allocating 0x1d72 pages at 0x00000000009ea000 alloc type 2

Loading 'mach_kernel'...

.....Error allocating 0x535 pages at 0x0000000000200000 alloc type 2

Error loading kernel 'mach_kernel' (0x9)

This happens when there is no AptioFix driver in /efi/drivers64UEFI folder, or when "slide=0" is not present in boot args when booting ML. So:

- double check your /efi/drivers64UEFI folder (not /efi/drivers64 folder) to have: FSInject-64.efi, HFSPlusX64.efi, OsxFatBinaryDrv-64.efi and OsxAptioFixDrv-64.efi, and nothing more.

- check if you have more then one config.plist in /efi/ folder and/or /efi/oem/.../folder - maybe you added slide=0 to the wrong one?

 

If above is setup correct, you should be able to boot in UEFI mode. Apart from being strange because it's new, he whole stuff is actually quite simple.

 

Should i move mach_kernel to the EFI partition? Should i have removed the Boot, Boot1 etc files and the EFI folder that's in the root of my OSX partition? (i left them alone because in case anything went wrong, like it went, i could aways boot from BIOS, which already works real nice for me). Perhaps, instead of copying the EFI folder and pasting it in the EFI partition, i should have only copied the contents of the EFI folder and put them there...? Any light on this subject would be much appreciated.

No need to move kernel anywhere.

And you can leave boot1, boot ... files on the stick - the same stick can be used for BIOS CloverEFI boot and UEFI boot. You can test both ways from USB stick. No need to install/copy it to EFI partition until it works fine.

Did you already install it to EFI partition? Are you maybe changing config.plist and drivers64UEFI on the stick but booting from HD? Or vice versa?

 

P.S.: where do i find the HFSPlus.efi file do you recommend? It's not inside CloverGrower (at least for me) and perhaps the one i used (as said before, i downloaded it elsewhere) is not the correct one (it's from an iMac 13,1).

HFSPlus.efi is not opensource and can not be packed with Clover. Post herecontains link to here with the latest one.

 

Good luck.

[theconnactic]

This happens when there is no AptioFix driver in /efi/drivers64UEFI folder, or when "slide=0" is not present in boot args when booting ML. So:

- double check your /efi/drivers64UEFI folder (not /efi/drivers64 folder) to have: FSInject-64.efi, HFSPlusX64.efi, OsxFatBinaryDrv-64.efi and OsxAptioFixDrv-64.efi, and nothing more.

- check if you have more then one config.plist in /efi/ folder and/or /efi/oem/.../folder - maybe you added slide=0 to the wrong one?

 

Thank you so much, dmazar! It was precisely this kind of info i was in need: concise, step by step troubleshooting. I'll try it in a couple of hours and report back.

 

 

No need to move kernel anywhere.

And you can leave boot1, boot ... files on the stick - the same stick can be used for BIOS CloverEFI boot and UEFI boot. You can test both ways from USB stick. No need to install/copy it to EFI partition until it works fine.

Did you already install it to EFI partition? Are you maybe changing config.plist and drivers64UEFI on the stick but booting from HD? Or vice versa?

 

I don't have an USB stick with Clover anymore, so i'm trying this with my main OSX partition. I already have Clover running in a smooth setup, albeit from BIOS. I want to try UEFI first because my board is UEFI, so why not use it?, second because i want to avoid resort to DSDT edits, since i'm so bad with it, third (but related to the second) because i want to try to use both my integrated and my discrete graphics card at the same time and, since i know it's possible with DSDT edits, perhaps i'll nail that using UEFI.

 

 

HFSPlus.efi is not opensource and can not be packed with Clover. Post herecontains link to here with the latest one. Good luck.

 

That's the one i already have. But thank you anyway.

 

Best regards!

 

EDIT: It worked! I don't understand why, since i own a Gigabyte UEFI board (the H77-DS3H), i needed to add these two other drivers (specially the Aptio one), but what really matters is it worked! Now i have both EFI and BIOS boot with clover. Thank you very much, dmazar!

 

I added also the CRMVideo driver, to get proper boot screen resolution, along the correct keys/strings under "Graphics" in the config.plist (i had already added my EDID from darwin dumper since i was using BIOS boot, much like with my netbook). Still no luck: the boot screen is inside a black frame circa two inches tick. I hope i have better luck with my system now, since its chipset is Intel. Here is my preboot.log: preboot.log.zip

 

UEFI boot didn't get both my cards (HD4000 and 9800GT) to work together, as i was expecting. On the contrary, when i enabled my internal graphics and set it as primary, Clover simply refused to boot from UEFI. Strange. But on the other hand, my system is booting in less than 20 seconds. Not bad for a system that relies on an old 2'5'' HDD scavenged from a broken EeePC 1005H.

[cwestpha]

I am having a hell of a time just getting Clover V2 to load in any mode (EFI or Legacy BIOS x64) on my Asus P8Z77-V Premium rig. Target is a SSD OCZ-Vertex 4 EFI partition (rdisk0s1) with OS X 10.8.2 (rdisk0s2) and I have failed to get Clover itself to load regardless of how I try to get it to work.

 

R1122 installer onto MBR /w Fat32 formatted 2 GB USB drive (Boot0 then latter Boot0hfs)

R1122 installer onto MBR /w HFS+ formatted USB drive (boot0hfs)

R1122 installer UEFI boot or MBR /w EFI/Fat32 on EFI disk0s1 (OS X's EFI partition)

R1122 installer MBR /w (hfs+) onto disk0s2 (OS X's main partition)

 

All of these end the same with the UEFI select loader screen coming up (as in after it fails to load anything and is confused how to proceed) or it reinitializes the screen and shows only a single underscore or number in the upper left hand screen. It never gives out a log, error, and provides any information as to what happened as if Clover V2 never loads no matter if I try to load it BIOS Legacy or UEFI Native. Its acting like if it couldn't find BOOT in a root directory.

 

Directory structure of EFI (disk0s1) is as follows:

boot

EFI/

… ACPI/ (contents are unchanged from default)

… BOOT/

config.plist (tried both original generic and customized with no difference)

…doc/ (contents are unchanged from default)

… driver64/

… … FSInject-64.efi

… … HFSPlus.efi

… … UsbMouseDxe-64.efi

… … VBoxExt4-64.efi

… … XhciDxe-64.efi-off

… drivers64UEFI/

… … CsmVideoDxe-64.efi-off

… … DataHubDxe-64.efi-off

… … EmuVariableUefi-64.efi-off

… … FSInject-64.efi

… … HFSPlus.efi

… … OsxAptioFixDrv-64.efi

… … OsxFatBinaryDrv-64.efi

… … OsxLowMemFixDrv-64.efi-off

… … PartitionDxe-64.efi-off

… kexts/ (contents are unchanged from default)

… misc/

… OEM/ (contents are unchanged from default)

… ROM/ (contents are unchanged from default)

… tools/

… … Shell32.efi

… … Shell64.efi

etc/

… rc.local

… rc.shutdown.local

 

Any ideas? I got Clover V2 booting MBR off of a different USB stick before and I just reformatted 10.8 so I could install it clean after getting it working well off of a different USB stick before. Alas it was my 8 GB stick and I needed to completely re-format that one so I could use it to re-install OS X for this attempt (I don't like having traces of old things left over if I am not using them like Chameleon or Chimera). I know I am missing something obvious or simple because 99% of the time those are the mistakes I make.

 

[update] Ok I got this working for some reason the R1122 release had a regression in it thats fixed in the R1133 package. However, now it work detect my OS X 10.8.2 install on the hard drive. It passes fine to Windows 8 EFI install and Ubuntu 12.10 EFI install. I even got it to detect and recognize an OS X ML installer (though that wont boot for obvius reasons). Any ideas or suggestions? I dont see where, if at all, it dumped out a debug output.