Clover General discussion

[wern apfel]

Since Yosemite i use Clover, so far no issues but FaceTime is only working without inserting an MLB number, is there an option to not insert automatically the Board Serial ?

[Ahmed_shiko]

need help yosemitePartition stuck in hibernate mode iam used Clover

[jamiethemorris]

Okay, I'm having a REALLY big problem... Clover won't patch any kexts unless it's booting to my Fusion drive. If I boot into my clone, none of my kext patches work. This includes ATI connectors patch. I tried creating an installer disk as well as installing Clover to another internal drive, but I got the same result - no kext patches, even for the installer. i was going to re-do my Fusion drive setup, but now I'm afraid to because I'm afraid after I rebuild it I'll never be able to get kext patching working again.

 

I tried this on both r2703 and r2850. EDIT: Also tested it on 2298, same result.

 

Am I the only one? I can't find a solution nor can I even find what is causing it. Please help.

 

EDIT 2: Also, it no longer selects my default boot device after upgrading to 2850.

[joe75]

can you post a bdmesg from the boot of the "clone" drive plz?

[jamiethemorris]

can you post a bdmesg from the boot of the "clone" drive plz?

I just get "boot-log" property not found.

 

Ok, so it seems like it magically fixed itself. I woke up this morning, and tried an older config.plist with a MacPro3,1 SMBios (normally I'm using 5,1), booted into another drive and all of a sudden kext patching is working. So I switched the config.plist back to my 5,1 plist and it's still working... I don't know what changed.

 

I have another question, how do I hide all these "UEFI Internal" entries? I was previously able to hide them with this:

 

<key>GUI</key>
<dict>
<key>Custom</key>
<dict>
<key>Entries</key>
<array>
<dict>
<key>Disabled</key>
<true/>
<key>FullTitle</key>
<string>UEFI Internal</string>
<key>Hidden</key>
<false/>
<key>Ignore</key>
<false/>
<key>InjectKexts</key>
<false/>
<key>NoCaches</key>
<false/>
<key>Type</key>
<string>Other</string>
</dict>
</array>
</dict>

[jamiethemorris]

I have an update... I decided to redo my fusion drive, now it's not working again. I have clover installed on both the clone and my fusion drive now. If i boot clover from the clone, kext patching only works on the clone drive. If I boot clover from the fusion drive, kext patching doesn't work on anything. This is truly bizarre.

 

I seriously want to throw my computer out the window right now.

 

Edit: correction. The trim patch and ahciport patch work. But none of the other patches do unless I boot my clone.

 

Edit 2: I ran kext utility on my main drive and kext patching is working properly again on both drives. Perhaps the kernel cache was just corrupted. All is well again, I no longer want to throw my computer out the window.

[joe75]

until the new problem comes along..

[jamiethemorris]

until the new problem comes along..

Indeed.

[Riley Freeman]

Well, with EmuVariableUefi it's like living with a gummy sex doll. When you enable real nvram, it's like the real woman is living with you now. So yes ... what can I say ...  expect some issues.

 

It looks like you might have fixed it with AptioFixNvramTest3 . Using it with r2830 and iLok is working fine. I'll keep an eye on it over the next day or so.

 

Update: No problems with Test3. On Test4 now and looking good so far.

[Ritz Carltn]

I have GTS 250(Tesla), pcie0, VideoPorts=2 and GTX 660Ti(Kepler), pcie1, VideoPorts=4 with Clover.

 

I used dsdt.aml atm,

In case of GTS 250(Tesla), it need injection and GTX 660Ti, don't need injection.

 

It was working both of all, except GTX660Ti vram 1024Mb, actually 2048MB.

 

Is there any good guide for dual GPU?

[Slice]

I have GTS 250(Tesla), pcie0, VideoPorts=2 and GTX 660Ti(Kepler), pcie1, VideoPorts=4 with Clover.

 

I used dsdt.aml atm,

In case of GTS 250(Tesla), it need injection and GTX 660Ti, don't need injection.

 

It was working both of all, except GTX660Ti vram 1024Mb, actually 2048MB.

 

Is there any good guide for dual GPU?

If you'll find a good way then report please.

[PencilNotPen]

Hi guys, this may have been asked before, but is it possible to set the Clover boot screen to 2560x1440 for an Apple Cinema Display? I have tried manually using ScreenResolution in config.plist, and by using PatchVBios, but neither work. Any suggestions welcome as it looks pretty ugly at the current resolution. It's a GTX 660 connected to ACD by dp-minidp if that matters.

Thanks!

[Slice]

Hi guys, this may have been asked before, but is it possible to set the Clover boot screen to 2560x1440 for an Apple Cinema Display? I have tried manually using ScreenResolution in config.plist, and by using PatchVBios, but neither work. Any suggestions welcome as it looks pretty ugly at the current resolution. It's a GTX 660 connected to ACD by dp-minidp if that matters.

Thanks!

This question was asked 37 times. Where can I put the answer for all to see?

PatchVBios=true

If not work then no way. That's all!

If someone has other answer then please open new thread.

[xpamamadeus]

Hi guys, this may have been asked before, but is it possible to set the Clover boot screen to 2560x1440 for an Apple Cinema Display? I have tried manually using ScreenResolution in config.plist, and by using PatchVBios, but neither work. Any suggestions welcome as it looks pretty ugly at the current resolution. It's a GTX 660 connected to ACD by dp-minidp if that matters.

Thanks!

In case u have uefi mobo and GOP enabled GTX 660 bios u need to disable CSM in bios and u will get 2560x1440 resolution without any config.plist tweaks.

If u need more help search forum or PM. 

[bronxteck]

actually slice i have a similar resolution issue on an HP elite book. if i use UEFI for boot clover's GUI resolution is correct at 1366x768 but if i boot verbose the text is out of frequency so it just looks like diagonal lines as it runs through the output. same for the stage 1 and stage 2 loading bars but the icon is correct resolution. now if i use Hybrid Bios UEFI/CSM boot the clover GUI will only load 1086x768 resolution and verbose and os loading bars are fine just a bit stretched out now here is where it gets weird. i used the clover iso you compiled and boot it with grub boot loader using this http://www.pendrivelinux.com/yumi-multiboot-usb-creator/ when i boot using this method the GUI and resolution is detected correctly. now my question is. is grub correcting the resolution or are you compiling the iso differently then your clover pkg. i also notice that booting this way it shows the clover revision that i am currently at not the ISO version. so as an example the iso i have is 2850 but clover displays my current 2858 and all of my existing configuration and kexts.

the reason i use the UEFI/CSM is that i can boot windows properly if i am in UEFI only i have to manually boot it through EFI file because clover just stops responding. it goes into a black terminal screen with no curser. i also have the same issue with clovers shell implementation. they just die. yet i can use another efishell and rename it shell64 and it works.

[PencilNotPen]

Thanks for the responses guys. Unfortunately my Z77-DS3H Bios has no CSM or GOP options that I can see. I guess I am stuck then. It is odd that it doesn't work with such a common display as the ACD. I would have thought a lot of people here would have encountered the problem, but I can't find any fixes on the forums anywhere...

[Slice]

actually slice i have a similar resolution issue on an HP elite book. if i use UEFI for boot clover's GUI resolution is correct at 1366x768 but if i boot verbose the text is out of frequency so it just looks like diagonal lines as it runs through the output. same for the stage 1 and stage 2 loading bars but the icon is correct resolution. now if i use Hybrid Bios UEFI/CSM boot the clover GUI will only load 1086x768 resolution and verbose and os loading bars are fine just a bit stretched out now here is where it gets weird. i used the clover iso you compiled and boot it with grub boot loader using this http://www.pendrivelinux.com/yumi-multiboot-usb-creator/ when i boot using this method the GUI and resolution is detected correctly. now my question is. is grub correcting the resolution or are you compiling the iso differently then your clover pkg. i also notice that booting this way it shows the clover revision that i am currently at not the ISO version. so as an example the iso i have is 2850 but clover displays my current 2858 and all of my existing configuration and kexts.

the reason i use the UEFI/CSM is that i can boot windows properly if i am in UEFI only i have to manually boot it through EFI file because clover just stops responding. it goes into a black terminal screen with no curser. i also have the same issue with clovers shell implementation. they just die. yet i can use another efishell and rename it shell64 and it works.

Sorry but I am not clear when you have good resolution and when is bad. What is UEFI/CSM and what is grub-efi. Why you load ISO by grub instead of boot from CD.

I am also not interested in third party pendrive creators. I have CLover installer that can prepare bootable USB stick. There is also a method to install Clover and Chameleon on the same HDD.

What is the problem with resolution in GUI and why it is different for different drives? May be just different configs?

[jlfilms]

Hey guys what directions do I follow To install Vanilla mavericks on my hackintosh? I got 10.8.5 right now.

 

Thanks

 

z77 ds3h board,

gtx 760 2gb gfx

i5 3570k 4.2ghz

[bronxteck]

i was just explaining what the different bios booting methods reflected with clover GUI. the bios has 3 options.... legacy which i did not mention, hybrid which is CSM/UEFI and UEFI. both UEFI and CSM have there own issues in GUI. which i stated above. in CSM it does not detect 1366x786 only a lower resolution is detected which is 1024x768 the question is. why if i use grub to boot clover iso directly is my screen detected correctly (1366x768). where as directly with clover it only see's 1024x768. is grub fixing clovers graphics VESA detection or is your iso compiled in a manner that is different from the clover package. one of the 2 wether its the iso or grub is fixing something in clover that normally is not working correctly for my machine. i only use the iso for clover recovery incase something goes wrong with a config. i do not normally use this method. clover is installed to my HDD efi partition. i also do not use patch vbios as it does not work for me.

[Stefan Milev]

Hi guys, as Toleda advised i will post here.

 

I want to achieve HDMI audio on GTX660 SC (4 ports - 2 DVI, HDMI and DP) only by Clover, without DSDT/SSDT in Mavericks and Yosemite. I did it by DSDT in Mavericks successfully, but I want to make the system more flexible.

I also had it before on HD5770 with Clover injection. 

 

Please advise.

Thanks

[joe75]

DSDT/SSDT is the more flexible fix because then its being injected with any boot you use.. In clover you inject Audio ID that you need and continue using toleda patches.

[Stefan Milev]

I see your point of view, but I wanted to keep the system DSDT free and do everything in Clover. 

[Slice]

i was just explaining what the different bios booting methods reflected with clover GUI. the bios has 3 options.... legacy which i did not mention, hybrid which is CSM/UEFI and UEFI. both UEFI and CSM have there own issues in GUI. which i stated above. in CSM it does not detect 1366x786 only a lower resolution is detected which is 1024x768 the question is. why if i use grub to boot clover iso directly is my screen detected correctly (1366x768). where as directly with clover it only see's 1024x768. is grub fixing clovers graphics VESA detection or is your iso compiled in a manner that is different from the clover package. one of the 2 wether its the iso or grub is fixing something in clover that normally is not working correctly for my machine. i only use the iso for clover recovery incase something goes wrong with a config. i do not normally use this method. clover is installed to my HDD efi partition. i also do not use patch vbios as it does not work for me.

Making boot.log (debug-log, preboot-log) will help you to see what is happen and help us to understand you.

[bronxteck]

thank you slice.

i guess i will take your suggestion and borrow a usb dvdrom and burn the iso to disk to clarify the issue. then i guess i will know what is correcting clover. if the disk still has the wrong resolution then grub is correcting video resolution at GUI.

[Slice]

thank you slice.

i guess i will take your suggestion and borrow a usb dvdrom and burn the iso to disk to clarify the issue. then i guess i will know what is correcting clover. if the disk still has the wrong resolution then grub is correcting video resolution at GUI.

It is not the answer I expected to see

Making boot.log (debug-log, preboot-log) will help you to see what is happen and help us to understand you.

 

"the disk still has the wrong resolution"

The disk has no resolution. It is a deal for config.plist and looking into boot.log will show you what are possible resolutions.