Jump to content
ErmaC

Clover General discussion

19,684 posts in this topic

Recommended Posts

Just to report OsxAptioFix3Drv-64.efi working well HP ProBook 6570B UEFI Boot

this is the more fast boot I ever see in macOS High SiERRA

Great job all Devs B)   only little things, verbose Boot 

 its print OsxAptioFix2Drv-64.efi Starting  overrides

 =======================

Share this post


Link to post
Share on other sites
Advertisement

4380 is borked here with AptioMemoryFix on my Samsung laptop.

 

First 10.11.6 attempt after reboot came up with a error allocating pages issue. Subsequent attempts cause a reboot instead of loading Clover menu.

 

Trying to boot 10.13.2 brings up a "does printf work" message.

 

4369 and AptioMemoryFix built from source was working fine.

 

Replacing AptioMemoryFix with my previous compiled version works fine, so the problem is with the copy bundled with 4380.

Share this post


Link to post
Share on other sites

..............siiiiiiiiiiiiigggggggggggggghhhhhhhhh........................AptioMemoryFix is just the same driver that is in clover but separated out from clover...... AptioFix3 is newest version of driver and the other two were reverted to their previous state, not sure why since they are inherently broken....

Share this post


Link to post
Share on other sites

Maybe there's something wrong with the copy of AptioFix3 in 4380?

 

Because it prints AptioFix2Drv in verbose mode and it fails to boot my Z68 in the same way that AptioFix2Drv does: error allocating pages. On the other hand, AptioMemoryFix boots it fine (the copy I compiled, not the one included with 4380).

Share this post


Link to post
Share on other sites

does aptiofix3 function similarly to aptiomemoryfix? in regards to native nvram function,as well as auto slide calc.

Can confirm that aptiofix3 of Clover_v2.4k_r4382 works flawless on my iMac Pro Skylake-X/X299 system. Nvram still native! No need for Emuvariable.. 

Share this post


Link to post
Share on other sites

Regards, Thank you for all the hard work you do. Guys can could explain the differences between the new options for the benefit of all, please.

 

1.AptioInputFix

2.AptioMemoryFix

3.OsxAptioFixDrv(1)(2)(3)

Share this post


Link to post
Share on other sites

However, no way to successfully boot my MacPro6,1 Broadwell-E/X99 System with aptiofix3 of Clover_v2.4k_r4382 without an adequate "slide" boot flag!

 

Again "printf" error!  

 

In contrary, AptioMemory.fix also works flawless on my MacPro6,1 Broadwell-E/X99 system.. 

Share this post


Link to post
Share on other sites

Slice, just noticed one thing;

 

My stalled at ++++++++++++ looks like wasn't AptioFix related but Clover.

 

The earliest version of clover I have is 4243, with that clover I can boot perfectly. Will try to test move versions to see what change results in freeze.

Share this post


Link to post
Share on other sites

However, no way to successfully boot my MacPro6,1 Broadwell-E/X99 System with aptiofix3 of Clover_v2.4k_r4382 without an adequate "slide" boot flag!

 

Again "printf" error!  

 

In contrary, AptioMemory.fix also works flawless on my MacPro6,1 Broadwell-E/X99 system.. 

i can boot without slide bootflag with aptiofix3drv on my X99 Haswell-E

Share this post


Link to post
Share on other sites

@devs & coders

with optiofix3 from clover rev 4380 system boots fine

I have tested nvram writing a variable with: 

sudo nvram MyVar="TestValue"

then I have rebooted my system and I have this allocation problem: it is related?

post-468967-0-37413900-1516177948_thumb.jpg

Edited by fabiosun

Share this post


Link to post
Share on other sites

Hi

 

Clover r4382: I don't no why AptioMemoryFix and AptioInputFix can't be compile (added) with Build_Clover.command v4.6.2? 

 

Idem with MaLdOn files Clover pkg see #16383

 

Thanks

Share this post


Link to post
Share on other sites

Has anyone experienced problems with English and your language after the update beta 5?

http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2565871

 

 

1, OsxAptioFix2Drv + EmuVariableUefi-64.efi

no problem.

 

2. new and old OsxAptioFixDrv/OsxAptioFix2Drv/OsxAptioFix3Drv without EmuVariableUefi-64.efi

problem above link

Share this post


Link to post
Share on other sites

Has anyone experienced problems with English and your language after the update beta 5?

http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2565871

 

 

1, OsxAptioFix2Drv + EmuVariableUefi-64.efi

no problem.

 

2. new and old OsxAptioFixDrv/OsxAptioFix2Drv/OsxAptioFix3Drv without EmuVariableUefi-64.efi

problem above link

Hello, try set your language via Terminal and "sudo languagesetup". After selecting your language you must restart.

Share this post


Link to post
Share on other sites

Hello, try set your language via Terminal and "sudo languagesetup". After selecting your language you must restart.

I know. But i just mentioned whether need

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

@devs & coders

with optiofix3 from clover rev 4380 system boots fine

I have tested nvram writing a variable with: 

sudo nvram MyVar="TestValue"

then I have rebooted my system and I have this allocation problem: it is related?

i can boot just fine after running nvram command, even though nvram native is not working

maybe bios setting ? 

Share this post


Link to post
Share on other sites

Has anyone experienced problems with English and your language after the update beta 5?

http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2565871

 

 

1, OsxAptioFix2Drv + EmuVariableUefi-64.efi

no problem.

 

2. new and old OsxAptioFixDrv/OsxAptioFix2Drv/OsxAptioFix3Drv without EmuVariableUefi-64.efi

problem above link

Setting language from Clover was excluded because "it is OS business"( ©Blusseau). Language for next reboot must be set by macOS itself not by Clover.

Share this post


Link to post
Share on other sites

Setting language from Clover was excluded because "it is OS business"( ©Blusseau). Language for next reboot must be set by macOS itself not by Clover.

Thank you for reply. So, realmac also must set language again after update? I don't have a realmac. I'm just curious this point.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

Thank you for reply. So, realmac also must set language again after update? I don't have a realmac. I'm just curious this point.

 

나의 LG-F800S 의 Tapatalk에서 보냄

No, the languge settings stored in NVRAM and update will be on your native language.

I am not sure because my computers usually speak english.

Share this post


Link to post
Share on other sites

No, the languge settings stored in NVRAM and update will be on your native language.

I am not sure because my computers usually speak english.

I checked nvram for lang. But there is no lang part in nvram. Only nvram of Lang part save after set lang in usb installer?

 

Emuvariable has prelang part in datacpuhub.c

 

I wonder when osx save lang part in nvram.

If user clear all nvram variables(sudo nvram -c), do we have to add lang typo in terminal?

 

Seems this part is not clarification.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

  • Similar Content

    • By metaphysician
      hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer

      i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
       
      however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
×