Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted

That's it? There is more to Clover than just that.

It is too complex sentence for my brain.

And there is also no file titled "boot1f32" in the ISO.

Screen Shot 2015-10-07 at 21.16.47.png

full name is boot1f32alt

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

Thank you everyone.  I finally have a working El Captain.

 

Question: When I install Clover EFI Bootloader r3280, i cannot boot to El Captain. I get this screen. Whatever I press it kept come to that screen,  I have to use Chris1111 v5 for installing Post installer to install Clover bootloader.  

sze7f6.jpg

Link to comment
Share on other sites
le0nardwashingt0n
le0nardwashingt0n
Posted
Posted

Thanks so much for all of your hard work on Clover, it's been so fun figuring out how to use this thing and make my pc boot mac. I have two questions for you all.

 

1) Why does clover display many _ symbols whenever I try to use this in the bootloader menus. For example, when I manually add nvda_drv=1 thirty or so _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ of these are displayed and I need to delete them. Is this just me, something I'm doing wrong, or a known issue? It's happened for several releases. A few other characters do it too, like the + and some others. Considering _ is so common in boot args, I figure this would be a bigger issue.

 

2) I know this question has been asked a million times but where is the best place to put kexts that don't need to be injected? I've heard the S/L/E vs EFI/Clover/Kexts/... debate but what about L/E? Someone mentioned it as a possibility in another thread and I hadn't heard that one before.

Link to comment
Share on other sites
karl001
karl001
Posted
Posted

i think I did that and I'm stuck with white screen with spinning colorful round icon.  But i will try again tonight.

 

I got the same problem. For me the cause was that the FakeSMC haven't been injected. I solved it by copying the needed kexts into the 10.10 folder also. It looks like clover thinks the installer is a 10.10 kernel or so.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

According to the project wiki, there is a boot1f32 that does not have a pause or selection capability in it. That is the one I wish to use.

OK, I will check why it is absent in ISO.

boot1f32.zip

Thank you everyone.  I finally have a working El Captain.

 

Question: When I install Clover EFI Bootloader r3280, i cannot boot to El Captain. I get this screen. Whatever I press it kept come to that screen,  I have to use Chris1111 v5 for installing Post installer to install Clover bootloader.  

sze7f6.jpg

Something wrong with your installation.

This screen mean you have legacy boot

BIOS->MBR->PBR->BOOT it shows this screen,

but then it searches the file /EFI/CLOVER/CLOVERX64.EFI and didn't find it.

 

 

@Slice why does clover detect dev = 0112 i5-2500k as HD2000 and same issue was in past and still clover hasn't fixed it .. 

Very old question numerous times discussed. It is HD2000, that's all.

Link to comment
Share on other sites
loganMac
loganMac
Posted
Posted

Something wrong with your installation.

This screen mean you have legacy boot

BIOS->MBR->PBR->BOOT it shows this screen,

but then it searches the file /EFI/CLOVER/CLOVERX64.EFI and didn't find it.

 

Rewritten and hopefully is understandable and clear. 

ASUS is UEFI bios.  What odd now is when I press DEL or F2 during post, I don't see UEFI on the drive icon. It is because I install Clover loader as Legacy? 

Here what I did to install El Capitan to USB.

 

Create USB El Capitan.

Terminal:

sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction

--> Successful making El Capitan USB

--> Install Clover r3280 to USB

--> I select same as screenshot

2zp8vew.jpg

--> Done

-- Edit Config.plist

  --> nv_disable=1

  --> NVidia=True

  --> AsusAICPUPM=True

--> Copy FakeSMC to USB/EFI/CLOVER/Kext/10.11

--> Done

 

Restart PC to boot from USB

  --> 1st initial installation was about 17min then PC reboot and continue it final installation. Successfully

 

--> Now on El Capitan Desktop.

       --> Install Clover r3280, I select the same selection as screenshot above

--> Edit Config.plist

  --> nvda_drv=1

  --> NVidia=False

  --> AsusAICPUPM=True

--> Copy FakeSMC to USB/EFI/CLOVER/Kext/10.11

--> Install Nvidia Web driver

Reboot PC to test if it works but I got this

sze7f6.jpg

 

Did I mistakenly did something wrong that's why I only get that screenshot above.

 

Note: EFI is folder inside El Capitan HDD

 

If I use Clover Config and mount, I see EFI drive. I forgot what in it.  I do know it's does not have CLOVER folder

 

My Bios setup: everything else default

Enabled: C3,C6,C1E, C Package, xHCI & EHCI Hand-off

Disabled: Intel Virt Tech

select these AHCI, PCIe

Boot: select both UEFi & Legacy

 

Update: I will use @asrsada's suggestion tonight

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

Intel's mistake.

 

As I said it was discussed. Don't repeat all pros and cons!

No mistake by Intel.

 

The i5-2500k has the same graphics that my i7-2600k has. It is HD3000.

 

Don't confuse i5-2500 with i5-2500k, nor i7-2600 with i7-2600k. The i5-2500 and i7-2600 have HD2000.

 

The data at ark.intel.com is correct for all.

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted

Or Maybe I should do this.

est54l.jpg

Use Drivers64UEFI (only). Also check Install Clover in ESP. You don't need to check "for UEFI only".

 

And try:

1. DataHubDxe-64

2. OSxAptioFix2Drv-64 (don't use them both)

3. PartitionDxe-64

 

Also, maybe try updating Clover? Last version is 3280.

 

It's very confusing what you did there...

 

So, to sum up:

 

Clover in ESP.

Check Drivers64UEFI and choose:

1. DataHubDxe-64

2. OSxAptioFix2Drv-64 (don't use them both)

3. PartitionDxe-64

 

Optionally Install RC Scripts on target volume.

And Install prefPane.

 

FakeSMC.kext and other 3rd party kexts that you might need to be injected on startup, put them in Clover/Kexts/10.11 (for El Capitan).

 

Also, for creating the USB drive, I wrote a step-by-step a while ago here, for Yosemite. The only difference should be the slightly different Disk Utility tool in El Capitan. See if it helps.

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

Re: HD2000 vs HD3000 

 

FYI...  have a i3-2125 on my H61N-USB3 board and it also is comes up as device x0112 HD2000 in clover - but when OS X boots its a different story. i "fixed" this issue long ago but putting device 0x0126 in the DSDT (and fixing the description).  I have a vague memory from 2-3 years  somewhere seeing the BIOS providing 2 devices IDs for the gfx board. like saying support for 112 or 126.  but its been so long i cant remember where I saw this.

 

 

2cents: Re: ESP Clover kext folder - 10.10 vs 10.11 vs Other

i have had good experience by putting all the kexts in ESP in /EFI/CLOVER/kexts/Other -- and removing the 10.x folders. Then one doesn't need worry about multiple copies and/or rev levels.  Note: I don't have any OS version dependent kexts in ESP. 

Link to comment
Share on other sites
insanelyDeepak
insanelyDeepak
Posted
Posted

Re: HD2000 vs HD3000 

 

FYI...  have a i3-2125 on my H61N-USB3 board and it also is comes up as device x0112 HD2000 in clover - but when OS X boots its a different story. i "fixed" this issue long ago but putting device 0x0126 in the DSDT (and fixing the description).  I have a vague memory from 2-3 years  somewhere seeing the BIOS providing 2 devices IDs for the gfx board. like saying support for 112 or 126.  but its been so long i cant remember where I saw this.

 

This way you are faking your Dev-ID which is not necessary 

Link to comment
Share on other sites
arsradu
arsradu
Posted
Posted
2cents: Re: ESP Clover kext folder - 10.10 vs 10.11 vs Other

i have had good experience by putting all the kexts in ESP in /EFI/CLOVER/kexts/Other -- and removing the 10.x folders. Then one doesn't need worry about multiple copies and/or rev levels.  Note: I don't have any OS version dependent kexts in ESP. 

 

We're gonna take your 2 cents. Though I'm not sure what we can get with those. :P

 

As it was discussed before, putting the kexts in Other folder and removing the other folders is not a problem. The problem is that, on next Clover installation, those folders will be added back automatically. And Clover will start looking for FakeSMC under /10.11 for El Capitan (just an example). Anyway, this is still open for debate, for as far as I know. :) Just wanted to bring you up to speed.

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

Re: HD2000 vs HD3000 

 

FYI...  have a i3-2125 on my H61N-USB3 board and it also is comes up as device x0112 HD2000 in clover - but when OS X boots its a different story. i "fixed" this issue long ago but putting device 0x0126 in the DSDT (and fixing the description).  I have a vague memory from 2-3 years  somewhere seeing the BIOS providing 2 devices IDs for the gfx board. like saying support for 112 or 126.  but its been so long i cant remember where I saw this.

0x112 and 0x122 are both HD3000 (my i7-2500k is 0x122). In both cases, injecting laptop HD3000 device-id works (no native support HD3000 desktop in OS X).

 

By default, Clover does the wrong thing here. Easily fixed with FakeID, /Devices/AddProperties, or /Devices/Arbitrary.

 

2cents: Re: ESP Clover kext folder - 10.10 vs 10.11 vs Other

i have had good experience by putting all the kexts in ESP in /EFI/CLOVER/kexts/Other -- and removing the 10.x folders. Then one doesn't need worry about multiple copies and/or rev levels.  Note: I don't have any OS version dependent kexts in ESP.

This is what I do as well. Now if the Clover installer pkg would stop re-creating the empty directories...

This way you are faking your Dev-ID which is not necessary

Unless you want to patch the kexts Info.plist, completely necessary. OS X does not support HD3000 desktop natively.

Link to comment
Share on other sites
insanelyDeepak
insanelyDeepak
Posted
Posted

0x112 and 0x122 are both HD3000 (my i7-2500k is 0x122). In both cases, injecting laptop HD3000 device-id works (no native support HD3000 desktop in OS X).

 

By default, Clover does the wrong thing here. Easily fixed with FakeID, /Devices/AddProperties, or /Devices/Arbitrary.

 

 

This is what I do as well. Now if the Clover installer pkg would stop re-creating the empty directories...

 

Unless you want to patch the kexts Info.plist, completely necessary. OS X does not support HD3000 desktop natively.

yes , you are right but i'm having full QE/CI with HD3000 i5-2500K , not using any fake-ID , just injected it in info.plist .. this was quite old issue when clover was in development but till now its detecting wrong 

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

yes , you are right but i'm having full QE/CI with HD3000 i5-2500K , not using any fake-ID , just injected it in info.plist .. this was quite old issue when clover was in development but till now its detecting wrong

FakeID is "update proof." Editing the plist is not.

Link to comment
Share on other sites
kjp4756
kjp4756
Posted
Posted

 --> Edit Conf.plist

  --> nvida_drv=1

  --> Nvidia=False

  --> AsusATCPUPM=True

--> Copy FakeSMC to USB/EFI/CLOVER/Kext/10.11

--> Install Nvidia Web driver

 

It should be nvda_drv=1 not nvidia_drv=1

Link to comment
Share on other sites
liujianwei
liujianwei
Posted
Posted

Hey there i use a T410 and my Vesa Resolution is not my screen resolution (1440x900). Is there any option of getting native resolution at boot without modding the VBIOS as it is part of my mobo bios?

Emulate a right BIOS maybe the only option.I don't think mod VBIOS or any BIOS can fix this problem,I have bricked two motherboard and one graphics card by mod BIOS or VBIOS.

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