Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

Guest
Guest
Posted
Posted

clover 4380 optiofix3 boots without slide value

with optiofix2 I have to put slide=128

 

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

Link to comment
Share on other sites
Guest
Guest
Posted
Posted (edited)

@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 Guest
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

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

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

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

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

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.

Link to comment
Share on other sites
Regi Yassin
Regi Yassin
Posted
Posted

@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 ? 

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

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.

  • Like 2
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

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에서 보냄

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

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.

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

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에서 보냄

Link to comment
Share on other sites
gujiangjiang
gujiangjiang
Posted
Posted

Hello slice.

 

A little suggestion on Clover Install Package.

 

Osxaptio drivers family may add describe information to clover package and I am willing to help translate the describe with these 5 drivers if you want.

 

Thanks.

 

 

从我的 iPhone 发送，使用 Tapatalk

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

I don't think so, but if you have some bios parameters to tweak for this allocation error I will try happily

 

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

maybe bios setting ? 

Link to comment
Share on other sites
telepati
telepati
Posted
Posted

Guys, I am so confused about NVRAM. if the system supports native NVRAM, is it create a nvram.plist in the EFI folder? Normally I am testing visually like that? I am looking Find My Mac and iMessage for the native NVRAM 'cause if these too work then the system support native NVRAM.  Before BIOS update my motherboard NVRAM support as a native. After the update, v3 BIOS native NVRAM is broked and I am using EmuVariableUefi-64.efi and OsxAptioFix2Drv.efi and checking Find My Mac and iMessage everything works.

 

Now I used these efi and it looks native NVRAM working 'cause imessage and find my mac working. is there a different way to test NVRAM working or not?

 

post-803029-0-24214800-1516209976_thumb.png

post-803029-0-31938700-1516210152_thumb.png

 

I also used @Sherlocks command from the clover change explanations thread;

 

sudo nvram boot-args="-v"

 

And system boots without any problem. But now every start system boots with verbose mode. I checked config.plist no any boot-arg how can I disable this command for normal boot?

 

 

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Guys, I am so confused about NVRAM. if the system supports native NVRAM, is it create a nvram.plist in the EFI folder? Normally I am testing visually like that? I am looking Find My Mac and iMessage for the native NVRAM 'cause if these too work then the system support native NVRAM. Before BIOS update my motherboard NVRAM support as a native. After the update, v3 BIOS native NVRAM is broked and I am using EmuVariableUefi-64.efi and OsxAptioFix2Drv.efi and checking Find My Mac and iMessage everything works.

 

Now I used these efi and it looks native NVRAM working 'cause imessage and find my mac working. is there a different way to test NVRAM working or not?

 

attachicon.gifScreen Shot 2018-01-17 at 20.10.48.png

attachicon.gifScreen Shot 2018-01-17 at 20.28.23.png

 

I also used @Sherlocks command from the clover change explanations thread;

 

sudo nvram boot-args="-v"

 

And system boots without any problem. But now every start system boots with verbose mode. I checked config.plist no any boot-arg how can I disable this command for normal boot?

Try sudo nvram -c and reboot

 

나의 LG-F800S 의 Tapatalk에서 보냄

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

You should not be using AptioMemoryFix and OsxAptioFixv3 together, use one or the other. Also delete the Nvram.plist from your EFI volume then open terminal and type sudo nvram -c and reboot

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

You should not be using AptioMemoryFix and OsxAptioFixv3 together, use one or the other. Also delete the Nvram.plist from your EFI volume then open terminal and type sudo nvram -c and reboot

 

Ok. Verbose mode disabled. 

Deleted Nvram.plist from EFI

Deleted AptioMemoryFix leave it OsxAptioFixv3 and Reboot.

 

post-803029-0-93654700-1516223390_thumb.png

 

iMessage and Find My Mac working. 

 

sudo nvram -p result look like that;

fakesmc-key-MSWr-ui8	%00
fakesmc-key-RPlt-ch8*	j95%00%00%00%00%00
EFILoginHiDPI	%00%00%00%00
fakesmc-key-RBr -ch8*	j95j95a%00
fmm-mobileme-token-FMM	bplist00%dc%01%02%03%04%05%06%07%08%09%0a%0b%0c%0d%0e%10%0d%11%0d%12%13%14%15%16%1d_%10%0funregisterState_%10%12enabledDataclassesYauthToken^disableContextVuserid]enableContextXusernameXpersonIDWaddTimeTguidXuserInfo_%10%13dataclassProperties%10%00%a1%0f_%10!com.apple.Dataclass.DeviceLocator_%10(AQAAAABaX7ie6TG-CkoeundPpjK4wKQIc-LeE8Q~%11%01%f5_%10%12muratozgul@mac.comY216605003#A%d6%97%ee(>%1f`_%10$15AC4698-1701-4441-8F76-9715B681CA62%d3%17%18%19%1a%1b%1c_%10%15InUseOwnerDisplayName_%10%13InUseOwnerFirstName_%10%12InUseOwnerLastName[Murat OzgulUMuratUOzgul%d1%0f%1e%d4%1f !"#$%25&VapsEnvXhostname]authMechanismVschemeZProduction_%10%13p71-fmip.icloud.comUtokenUhttps%00%08%00!%003%00H%00R%00a%00h%00v%00%7f%00%88%00%90%00%95%00%9e%00%b4%00%b6%00%b8%00%dc%01%07%01%0a%01%1f%01)%012%01Y%01`%01x%01%8e%01%a3%01%af%01%b5%01%bb%01%be%01%c7%01%ce%01%d7%01%e5%01%ec%01%f7%02%0d%02%13%00%00%00%00%00%00%02%01%00%00%00%00%00%00%00'%00%00%00%00%00%00%00%00%00%00%00%00%00%00%02%19
fakesmc-key-#KEY-ui32	%00%00%00%10
SystemAudioVolumeDB	%f0
fakesmc-key-BATP-flag	%00
EFIBluetoothDelay	%b8%0b
fakesmc-key-MSTc-ui8	%00
LocationServicesEnabled	%01
fakesmc-key-BNum-ui8	%00
security-mode	none
csr-active-config	g%00%00%00
fakesmc-key-$Num-ui8	%01
fakesmc-key-MSFW-ui8	%01%00
fakesmc-key-REV -ch8*	%023%0f%00%00%10
fakesmc-key-MSPS-ui16	%00%03
fmm-computer-name	Murat%e2%80%99s Mac
bootercfg	(%00
fakesmc-key-$Adr-ui32	%00%00%03%00
fakesmc-key-EPCI-ui32	%08%c0%f0%00
bluetoothActiveControllerInfo	%8d%82%ac%05%01%00%00%00s%14%b4%18%d1%e7^%8c
fakesmc-key-MSAc-ui16	%00%00
SystemAudioVolume	0
fakesmc-key-RMde-char	A
flagstate	%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00
bluetoothInternalControllerInfo	%8d%82%ac%05%00%00s%14%b4%18%d1%e7^%8c
fakesmc-key-BEMB-flag	%00

is that mean my nvram now working as a native?

Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted

Ok. Verbose mode disabled. 

Deleted Nvram.plist from EFI

Deleted AptioMemoryFix leave it OsxAptioFixv3 and Reboot.

 

attachicon.gifScreen Shot 2018-01-18 at 00.09.03.png

 

iMessage and Find My Mac working. 

 

sudo nvram -p result look like that;

fakesmc-key-MSWr-ui8	%00
fakesmc-key-RPlt-ch8*	j95%00%00%00%00%00
EFILoginHiDPI	%00%00%00%00
fakesmc-key-RBr -ch8*	j95j95a%00
fmm-mobileme-token-FMM	bplist00%dc%01%02%03%04%05%06%07%08%09%0a%0b%0c%0d%0e%10%0d%11%0d%12%13%14%15%16%1d_%10%0funregisterState_%10%12enabledDataclassesYauthToken^disableContextVuserid]enableContextXusernameXpersonIDWaddTimeTguidXuserInfo_%10%13dataclassProperties%10%00%a1%0f_%10!com.apple.Dataclass.DeviceLocator_%10(AQAAAABaX7ie6TG-CkoeundPpjK4wKQIc-LeE8Q~%11%01%f5_%10%12muratozgul@mac.comY216605003#A%d6%97%ee(>%1f`_%10$15AC4698-1701-4441-8F76-9715B681CA62%d3%17%18%19%1a%1b%1c_%10%15InUseOwnerDisplayName_%10%13InUseOwnerFirstName_%10%12InUseOwnerLastName[Murat OzgulUMuratUOzgul%d1%0f%1e%d4%1f !"#$%25&VapsEnvXhostname]authMechanismVschemeZProduction_%10%13p71-fmip.icloud.comUtokenUhttps%00%08%00!%003%00H%00R%00a%00h%00v%00%7f%00%88%00%90%00%95%00%9e%00%b4%00%b6%00%b8%00%dc%01%07%01%0a%01%1f%01)%012%01Y%01`%01x%01%8e%01%a3%01%af%01%b5%01%bb%01%be%01%c7%01%ce%01%d7%01%e5%01%ec%01%f7%02%0d%02%13%00%00%00%00%00%00%02%01%00%00%00%00%00%00%00'%00%00%00%00%00%00%00%00%00%00%00%00%00%00%02%19
fakesmc-key-#KEY-ui32	%00%00%00%10
SystemAudioVolumeDB	%f0
fakesmc-key-BATP-flag	%00
EFIBluetoothDelay	%b8%0b
fakesmc-key-MSTc-ui8	%00
LocationServicesEnabled	%01
fakesmc-key-BNum-ui8	%00
security-mode	none
csr-active-config	g%00%00%00
fakesmc-key-$Num-ui8	%01
fakesmc-key-MSFW-ui8	%01%00
fakesmc-key-REV -ch8*	%023%0f%00%00%10
fakesmc-key-MSPS-ui16	%00%03
fmm-computer-name	Murat%e2%80%99s Mac
bootercfg	(%00
fakesmc-key-$Adr-ui32	%00%00%03%00
fakesmc-key-EPCI-ui32	%08%c0%f0%00
bluetoothActiveControllerInfo	%8d%82%ac%05%01%00%00%00s%14%b4%18%d1%e7^%8c
fakesmc-key-MSAc-ui16	%00%00
SystemAudioVolume	0
fakesmc-key-RMde-char	A
flagstate	%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00
bluetoothInternalControllerInfo	%8d%82%ac%05%00%00s%14%b4%18%d1%e7^%8c
fakesmc-key-BEMB-flag	%00

is that mean my nvram now working as a native?

Seems to be working to me

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

Seems to be working to me

 

Thank you. I also tried just AptioMemoryFix.efi this is worked too. You said dont use both same time but when I used both system boots super fast I dont know why?

 

AptioMemoryFix boot time 13s

OsxAptioFixv3 boot time 13s

Both 8s

 

BTW, how should I know which one is better for my system AptioMemoryFix.efi or OsxAptioFixv3.efi? What is the differences?

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