1667 replies to this topic

[theconnactic]

dmazar, on 18 February 2013 - 10:18 PM, said:

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.

dmazar, on 18 February 2013 - 10:18 PM, said:

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.

dmazar, on 18 February 2013 - 10:18 PM, said:

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   3.39K   0 downloads

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.

[k3nny]

@cwestpha:
You need to read the instruction posts first. Clover has many possible setup combinations and options and you will need to find the right one:
http://www.insanelym.../#entry1852956. Also take a look at the other posts in that thread.

For an UEFI boot:
- Turn off Secure Boot in your BIOS. Otherwise no other EFI application except Windows bootloader will start.
- Set UEFI device prioritisation in Compatibility Support Module (CMS) or disable it completely
- Delete unnecessary drivers from drivers64UEFI. Most probably you will just need OsxFatBinary, OsxAptioFix and HFSPlus.
- If OsxAptioFix is being used: Add slide=0 as a boot argument into the config file
When Clover finally starts, you can enter a special menu point called "Clover Boot Options" or similar to create a boot entry.

Edited by k3nny, 19 February 2013 - 01:01 PM.

[cwestpha]

k3nny, on 19 February 2013 - 02:01 AM, said:

@cwestpha:
You need to read the instruction posts first. Clover has many possible setup combinations and options and you will need to find the right one:
http://www.insanelym.../#entry1852956. Also take a look at the other posts in that thread.

For an UEFI boot:
- Turn off Secure Boot in your BIOS. Otherwise no other EFI application except Windows bootloader will start.
- Turn off CSM if your hardware supports it
- Delete unnecessary drivers from drivers64UEFI. Most probably you will just need OsxFatBinary, OsxAptioFix and HFSPlus.
- If OsxAptioFix is being used: Add slide=0 as a boot argument into the config file
When Clover finally starts, you can enter a special menu point called "Clover Boot Options" or similar to create a boot entry.

The problem is I have already read the thread and followed the instructions and been unable to replicate my former working setup from USB drive under any circumstance or combination. My problem is not loading the OS yet, its just getting Clover to initialize which it refuses to do. Either the UEFI loader on my motherboard refuses to load it or the moment it starts loading it just fails before there is any indication what failed. Good point on the CSM, already have the slide option set and secure boot disabled... good point on the CSM, though I didn't need to disable that before to get Clover to work

[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.

[theconnactic]

Hi, k3nny!

Is it really needed to turn off CSM (Compatibility Support Mode)? I keep it enabled on my board and yet, after lots of failures and the providential help offered by dmazar, i got it to boot. In what ways can it prevent Clover to work?

Best regards!

[cwestpha]

theconnactic, on 19 February 2013 - 03:06 AM, said:

Hi, k3nny!

Is it really needed to turn off CSM (Compatibility Support Mode)? I keep it enabled on my board and yet, after lots of failures and the providential help offered by dmazar, i got it to boot. In what ways can it prevent Clover to work?

Best regards!

CSM is a compatibility module written for the base uEFI thats just included in the firmware by the manufacturer to try and make life "easier" and give better backwards computability. It handles and automates some things not included in the uEFI base standard that the firmware didnt include at the time and supports things like BIOS booting and hybrid OS installs (that is when the OS expects elements of BIOS and EFI. Thing is EFI is still so new that there isn't a "right" or "wrong" way to do things or add backwards compatibility, so some of the time it will cause undesired side-effects or just cause things to fail. Ideally clover V2 should be booted purely off of a standard uEFI platform as a EFI native loader. Sometimes the CSM can misbehave and cause things to load or not load, its detection code mess up and pass bad options to the uEFI firmware causing extra entries in the bootable devices list, etc.
Its one thing to have a standard, but until people get used to it and start working with best practices discovering how everything should interconnect you get confusion and crappy CSMs.

[theconnactic]

Thank you for the information, cwestpha!

Since it doesn't do any good, and it can actually bring issues, i turned it off, too.

Best regards.

[ErmaC]

magnifico, on 18 February 2013 - 06:23 PM, said:

New Theme By Magnifico

We will add soon in the first pages...

ErmaC

[antoniodapc]

Why if you put the Fix Icloud, iCloud I just can not get it to work?
Please Helpme

[dmazar]

theconnactic, on 19 February 2013 - 03:46 AM, said:

Since it doesn't do any good, and it can actually bring issues, i turned it off, too.

About that CSM (Compatibility Support Module) - this is a "small BIOS" embedded into UEFI. It is here to allow you to do legacy BIOS boot (MBR -> PBR -> OS plus all needed BIOS services to start legacy OS). If you turn it off, then you can no longer do BIOS boot, for example can not longer boot with boot0->boot1->boot (CloverEFI or Chameleon) and can no longer start BIOS installed Windows for example. You can only do pure UEFI boot. Plus, you can no longer use devices which have only legacy (BIOS) option ROMs, like most graphics cards today (driver is called video bios, VBIOS - BIOS graphics driver for the card). Where "no longer use" here means: no use of them during boot - once OS is booted it can still start it's own drivers and use those devices.

Turning CSM off requires having native UEFI GOP graphics driver for your card. GOP stands for Graphics Output Protocol and is part of UEFI specification - defines programming interface for graphics display for UEFI drivers and applications (bootloaders). UEFI GOP driver for Intel HD graphics is probably present in all UEFIs and you can probably turn off CSM and use Intel HD.

But when it comes to various PCI graphics cards, then turning CSM off requires GOP driver for that card and not VBIOS any more. VBIOS can be used only in BIOS - or in UEFI with CSM turned on. CsmVideo driver that we use to enable higher res on our UEFIs is actually part of CSM module - it is driver which publishes GOP interface to the rest of UEFI on one side, but on the other side uses BIOS calls to card's VBIOS to do actual graphics stuff. And that driver, obviously, requires CSM to be turned on - if that driver is going to be used at all. In short: if CSM is off, then CsmVideo driver can be removed from drivers64UEFI dir - it will not work any more.

Graphics card vendors can embed VBIOS or GOP or both drivers into their cards, but as far as I saw, they usually do not have enough space for embedding both of them and, for now, they choose to embed VBIOS driver. Having video card with VBIOS and having CSM turned on still allows boot on UEFI systems, both UEFI and legacy BIOS boot. While having only GOP driver embedded into the card would make this card useless in BIOS systems and/or UEFI systems when doing legacy BIOS boot.
In short: if turning CSM off, you need GOP driver for the video card.

[Slice]

k3nny, on 19 February 2013 - 02:01 AM, said:

- Turn off CSM if your hardware supports it

I always keep CSM enabled.

cwestpha, on 19 February 2013 - 02:37 AM, said:

[update]  Any ideas or suggestions? I dont see where, if at all, it dumped out a debug output.

Sorry, I didn't understand your question. As I see you have success with 1133.
You can get debug output if uncomment in refit.conf the line
#systemlog

antoniodapc, on 19 February 2013 - 09:26 AM, said:

Why if you put the Fix Icloud, iCloud I just can not get it to work?
Please Helpme

If you speak about latest revision then it is strange. It will work with any combinations of keys.
Check your SMBIOS produced by DarwinDumper.

[xpamamadeus]

theconnactic, on 19 February 2013 - 01:15 AM, said:

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.

Hi i can help u with getting both card work in UEFI
First of all u will need to google for "[Easy Guide] ML: HDMI Audio/HD4000/7 Series MB" to make dsdt.
With that dsdt u need to set  intel as a primary and turn off graphics enabler and u will get hdmi audio too.
I have similar setup with Z77x UD5H and hd4000 and nvidia gtx 660 as second card all with clover UEFI working perfect.
Without that dsdt i cannon boot ml becouse HD 4000 need graphics enabler=Yes and nvidia need it =No soo dsdt its a must.

These drivers are needed for UEFI boot  Drivers64 UEFI.JPG   13.01K   11 downloads
,soo if u have more than that delete it.
If u need more help for bios settings i can post SS of it.
I see u added CSMvideodriver,u must delete it if ur using intel as primary,i get just blank screen with it.

[antoniodapc]

Slice, on 19 February 2013 - 10:47 AM, said:

If you speak about latest revision then it is strange. It will work with any combinations of keys.
Check your SMBIOS produced by DarwinDumper.

now that I made the dump as I proceed

[theconnactic]

Hi, xpamamadeus!

I already got bot cards to work at the same time with legacy BIOS (and yes, dmazar: CSM is turned off in my BIOS settings) using a DSDT patch provided by Toleda, as you can see here: http://www.insanelym...e/#entry1890275

When i tried to do the same with UEFI, i was getting a black (blank) screen even before the Clover screen loaded, so i couldn't even boot - i was using the CRMVideoDriver.efi, so i remove it as you told me to do. Now, what i got is the cursor blinking forever, and i still never get to the Clover boot screen, so i'm still stuck.

Thank you!

EDIT: I got to the boot menu by editing my config.plist, removing PatchVBIOS=Yes - which was what was preventing me to boot - and letting only GraphicsInjector=No there. However, i got a stretched boot menu/boot screen by doing that, and the system undergoes heavy graphics artifacts when it finally boots to the desktop, to the point of being unusable.

Could you share with me what's the exact settings you're using under Graphics to boot UEFI with Clover with two cards?

Thank you very much!

[magnifico]

There 's something that I convine in the latest revisions, I still have to get to a slowdown in GUI ....mhmm...ufff

But why ?

Damzar ?

[xpamamadeus]

theconnactic, on 19 February 2013 - 03:46 PM, said:

Hi, xpamamadeus!

I already got bot cards to work at the same time with legacy BIOS (and yes, dmazar: CSM is turned off in my BIOS settings) using a DSDT patch provided by Toleda, as you can see here: http://www.insanelym...e/#entry1890275

When i tried to do the same with UEFI, i was getting a black (blank) screen even before the Clover screen loaded, so i couldn't even boot - i was using the CRMVideoDriver.efi, so i remove it as you told me to do. Now, what i got is the cursor blinking forever, and i still never get to the Clover boot screen, so i'm still stuck.

Thank you!

EDIT: I got to the boot menu by editing my config.plist, removing PatchVBIOS=Yes - which was what was preventing me to boot - and letting only GraphicsInjector=No there. However, i got a stretched boot menu/boot screen by doing that, and the system undergoes heavy graphics artifacts when it finally boots to the desktop, to the point of being unusable.

Could you share with me what's the exact settings you're using under Graphics to boot UEFI with Clover with two cards?

Thank you very much!

in config under graphics i have only graphicsinjector=No
Nothing more.

[theconnactic]

xpamamadeus, on 19 February 2013 - 05:19 PM, said:

in config under graphics i have only graphicsinjector=No
Nothing more.

I was, in a certain degree, fearing you just say that: now i know it's some kind of exoteric issue that will give me a headache to solve, lol. Anyway, i'll post a video dump in a couple of minutes.

As a side note: the more i use Clover, the more awed i become because of how powerful it is. Video dumps used to be a goodie you could only have with Linux - via command line - or with third party solutions. Congrats to all developers.

P.S.: Here's the video dump:  c0000.bin.zip   37.1K   6 downloads

[xpamamadeus]

theconnactic, on 19 February 2013 - 05:58 PM, said:

I was, in a certain degree, fearing you just say that: now i know it's some kind of exoteric issue that will give me a headache to solve, lol. Anyway, i'll post a video dump in a couple of minutes.

As a side note: the more i use Clover, the more awed i become because of how powerful it is. Video dumps used to be a goodie you could only have with Linux - via command line - or with third party solutions. Congrats to all developers.

P.S.: Here's the video dump: c0000.bin.zip

Post bios screen shots

[theconnactic]

xpamamadeus, on 19 February 2013 - 07:25 PM, said:

Post bios screen shots

How do i do that? Don't have a cam. If there's some built-in screenshot tool under Gigabyte UEFI, though, it would be possible. Which of the sections of the BIOS should i post here, in case i have this possibility?

[xpamamadeus]

theconnactic, on 19 February 2013 - 07:38 PM, said:

How do i do that? Don't have a cam. If there's some built-in screenshot tool under Gigabyte UEFI, though, it would be possible. Which of the sections of the BIOS should i post here, in case i have this possibility?

use fat32 usb stick and press f12 to capture screen

Post peripherals and CSM support options.