Jump to content
ErmaC

Clover General discussion

20,227 posts in this topic

Recommended Posts

Hi, is anyone intrested in try this version of FileNVRAM.kext in Clover EFI?

 

Requirement:

1) backup your existent nvram.plist (to be restored later)

2) boot from usb (for safety)

3) report (e.g. if if you can load web drivers using only the Nvidia manager or anything else)

 

This kext is done for Clover and do not write anything on your hd, but that should be done by your rc script.

FileNVRAM.kext.zip

Share this post


Link to post
Share on other sites
Advertisement

Ok, but I still got this error with r4047...

boot6
                             <--------------------------------------------------
TOOLCHAIN_DIR: /Users/vanilla/src/opt/local
NASM_PREFIX: /Users/vanilla/src/opt/local/bin/
NASM_VER: 2.12.02
Initializing workspace
Loading previous configuration from /Users/vanilla/src/edk2/Conf/BuildEnv.sh
WORKSPACE: /Users/vanilla/src/edk2
EDK_TOOLS_PATH: /Users/vanilla/src/edk2/BaseTools
CONF_PATH: /Users/vanilla/src/edk2/Conf

Running edk2 build for CloverX64 using the command:
build  -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_LOW_EBDA -p Clover/Clover.dsc  -a X64 -b RELEASE -t XCODE5 -n 5 

Build environment: Darwin-16.6.0-x86_64-i386-64bit
Build start time: 04:32:55, Mar.30 2017

WORKSPACE        = /Users/vanilla/src/edk2
ECP_SOURCE       = /Users/vanilla/src/edk2/EdkCompatibilityPkg
EDK_SOURCE       = /Users/vanilla/src/edk2/EdkCompatibilityPkg
EFI_SOURCE       = /Users/vanilla/src/edk2/EdkCompatibilityPkg
EDK_TOOLS_PATH   = /Users/vanilla/src/edk2/BaseTools
CONF_PATH        = /Users/vanilla/src/edk2/Conf


Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE5

Active Platform          = /Users/vanilla/src/edk2/Clover/Clover.dsc
Flash Image Definition   = /Users/vanilla/src/edk2/Clover/Clover.fdf

Processing meta-data .......... done!
Building ... /Users/vanilla/src/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64]
Building ... /Users/vanilla/src/edk2/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf [X64]
Building ... /Users/vanilla/src/edk2/MdePkg/Library/BaseMemoryLib/BaseMemoryLib.inf [X64]
make: Nothing to be done for `tbuild'.
Building ... /Users/vanilla/src/edk2/MdePkg/Library/BaseLib/BaseLib.inf [X64]
make: Nothing to be done for `tbuild'.
Building ... /Users/vanilla/src/edk2/MdePkg/Library/BasePrintLib/BasePrintLib.inf [X64]
make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
Building ... /Users/vanilla/src/edk2/MdePkg/Library/BaseReportStatusCodeLibNull/BaseReportStatusCodeLibNull.inf [X64]
Building ... /Users/vanilla/src/edk2/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic.inf [X64]
make: Nothing to be done for `tbuild'.
Building ... /Users/vanilla/src/edk2/MdeModulePkg/Library/DxeCoreMemoryAllocationLib/DxeCoreMemoryAllocationLib.inf [X64]
Building ... /Users/vanilla/src/edk2/MdePkg/Library/DxeCoreEntryPoint/DxeCoreEntryPoint.inf [X64]
Building ... /Users/vanilla/src/edk2/MdePkg/Library/UefiRuntimeServicesTableLib/UefiRuntimeServicesTableLib.inf [X64]
/Users/vanilla/src/edk2/MdePkg/Library/BasePrintLib/PrintLibInternal.c:713:23: error: cannot compile this va_arg expression yet
              Width = VA_ARG (VaListMarker, UINTN);
                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Include/Base.h:672:124: note: expanded from macro 'VA_ARG'
#define VA_ARG(Marker, TYPE)         ((sizeof (TYPE) < sizeof (UINTN)) ? (TYPE)(__builtin_va_arg (Marker, UINTN)) : (TYPE)(__builtin_va_arg (Marker, TYPE)))
                                                                                                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Library/BasePrintLib/PrintLibInternal.c:719:27: error: cannot compile this va_arg expression yet
              Precision = VA_ARG (VaListMarker, UINTN);
                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Include/Base.h:672:124: note: expanded from macro 'VA_ARG'
#define VA_ARG(Marker, TYPE)         ((sizeof (TYPE) < sizeof (UINTN)) ? (TYPE)(__builtin_va_arg (Marker, UINTN)) : (TYPE)(__builtin_va_arg (Marker, TYPE)))
                                                                                                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Library/BasePrintLib/PrintLibInternal.c:812:21: error: cannot compile this va_arg expression yet
            Value = VA_ARG (VaListMarker, int);
                    ^~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Include/Base.h:672:81: note: expanded from macro 'VA_ARG'
#define VA_ARG(Marker, TYPE)         ((sizeof (TYPE) < sizeof (UINTN)) ? (TYPE)(__builtin_va_arg (Marker, UINTN)) : (TYPE)(__builtin_va_arg (Marker, TYPE)))
                                                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Library/BasePrintLib/PrintLibInternal.c:818:21: error: cannot compile this va_arg expression yet
            Value = VA_ARG (VaListMarker, INT64);
                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Include/Base.h:672:124: note: expanded from macro 'VA_ARG'
#define VA_ARG(Marker, TYPE)         ((sizeof (TYPE) < sizeof (UINTN)) ? (TYPE)(__builtin_va_arg (Marker, UINTN)) : (TYPE)(__builtin_va_arg (Marker, TYPE)))
                                                                                                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Library/BasePrintLib/PrintLibInternal.c:909:28: error: cannot compile this va_arg expression yet
          ArgumentString = VA_ARG (VaListMarker, CHAR8 *);
                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Include/Base.h:672:124: note: expanded from macro 'VA_ARG'
#define VA_ARG(Marker, TYPE)         ((sizeof (TYPE) < sizeof (UINTN)) ? (TYPE)(__builtin_va_arg (Marker, UINTN)) : (TYPE)(__builtin_va_arg (Marker, TYPE)))
                                                                                                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Library/BasePrintLib/PrintLibInternal.c:927:23: error: cannot compile this va_arg expression yet
          Character = VA_ARG (VaListMarker, UINTN) & 0xffff;
                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Include/Base.h:672:124: note: expanded from macro 'VA_ARG'
#define VA_ARG(Marker, TYPE)         ((sizeof (TYPE) < sizeof (UINTN)) ? (TYPE)(__builtin_va_arg (Marker, UINTN)) : (TYPE)(__builtin_va_arg (Marker, TYPE)))
                                                                                                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Library/BasePrintLib/PrintLibInternal.c:937:21: error: cannot compile this va_arg expression yet
          TmpGuid = VA_ARG (VaListMarker, GUID *);
                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Include/Base.h:672:124: note: expanded from macro 'VA_ARG'
#define VA_ARG(Marker, TYPE)         ((sizeof (TYPE) < sizeof (UINTN)) ? (TYPE)(__builtin_va_arg (Marker, UINTN)) : (TYPE)(__builtin_va_arg (Marker, TYPE)))
                                                                                                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Library/BasePrintLib/PrintLibInternal.c:970:21: error: cannot compile this va_arg expression yet
          TmpTime = VA_ARG (VaListMarker, TIME *);
                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Include/Base.h:672:124: note: expanded from macro 'VA_ARG'
#define VA_ARG(Marker, TYPE)         ((sizeof (TYPE) < sizeof (UINTN)) ? (TYPE)(__builtin_va_arg (Marker, UINTN)) : (TYPE)(__builtin_va_arg (Marker, TYPE)))
                                                                                                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Library/BasePrintLib/PrintLibInternal.c:994:20: error: cannot compile this va_arg expression yet
          Status = VA_ARG (VaListMarker, RETURN_STATUS);
                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/vanilla/src/edk2/MdePkg/Include/Base.h:672:124: note: expanded from macro 'VA_ARG'
#define VA_ARG(Marker, TYPE)         ((sizeof (TYPE) < sizeof (UINTN)) ? (TYPE)(__builtin_va_arg (Marker, UINTN)) : (TYPE)(__builtin_va_arg (Marker, TYPE)))
                                                                                                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9 errors generated.
make: *** [/Users/vanilla/src/edk2/Build/Clover/RELEASE_XCODE5/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/PrintLibInternal.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/vanilla/src/edk2/Build/Clover/RELEASE_XCODE5/X64/MdePkg/Library/BasePrintLib/BasePrintLib]


build.py...
 : error F002: Failed to build module
	/Users/vanilla/src/edk2/MdePkg/Library/BasePrintLib/BasePrintLib.inf [X64, XCODE5, RELEASE]

- Failed -
Build end time: 04:33:09, Mar.30 2017
Build total time: 00:00:14

[EDIT]

Well, still this error in r4046, everything seems the same as the previous r4045 here...

Note: Both r4047 and r4046 were compiled with Xcode 8.3 (but failed)

 

[EDIT 2]

Oops. Forgot to apply the patches of EDK2! Now everything works, thanks @Zenith432!

Edited by PMheart

Share this post


Link to post
Share on other sites

Hi, is anyone intrested in try this version of FileNVRAM.kext in Clover EFI?

 

Requirement:

1) backup your existent nvram.plist (to be restored later)

2) boot from usb (for safety)

3) report (e.g. if if you can load web drivers using only the Nvidia manager or anything else)

 

This kext is done for Clover and do not write anything on your hd, but that should be done by your rc script.

 

hello micky
first, thank you for great kext. 
i want to accurately know it how i can use it.
 
should remove all rc script? and only use your kext? i can test brightness value in my laptop

Share this post


Link to post
Share on other sites

Hi, is anyone intrested in try this version of FileNVRAM.kext in Clover EFI?

 

Requirement:

1) backup your existent nvram.plist (to be restored later)

2) boot from usb (for safety)

3) report (e.g. if if you can load web drivers using only the Nvidia manager or anything else)

 

This kext is done for Clover and do not write anything on your hd, but that should be done by your rc script.

@Micky1979 - what does this kext do specifically? what do I look for ?

 

happy to test. should I presume this kext is just for a machine where one needs EmuVariable?

Share this post


Link to post
Share on other sites

Hi Sherlocks. The kext does not write anything, so you still need the rc scripts. Yes, brightness setting here show up..

Okay.

Q. When normal boot, read nvram.plist in ESP, now rc script make nvram.plist when reboot or shutdown. Like you mention 1, backup nvram, what means it? Remove?

 

Q. If remove nvram.plist in ESP until reboot or shutdown, when reboot or shutdown rc script automately make nvram.plist. no choice nvram clear. Need to disable rc script. No relate?

 

Q. Can i check debug result? Just check nvram -p in terminal? What is NVRAM.kext's goal?

 

Thanks in advance

 

나의 LG-F410S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

It's my fork of meklor's FileNVRAM. I'm writing from my smartphone so I cannot link the source, but just search my repo and you will see it.

Yes this should be used with legacy bioses, but you can use that as well in UEFI if you want emulated nvram Lol.

The fact is that you can have more vanilla vars in nvram, like preferred networks, power management, audio volume etc. Also you can use the nvram command line as you wish. The kext is usually read write and you can make it read-only with -FileNVRAMro flag (automatically set in code for this test). So you still need the rc script working. It's a test for now.

Share this post


Link to post
Share on other sites

Stay tuned

 

Edit: Rev 4046

hello

 

very good work

 

the last 2 builds working with last xcode ..

 

Captura de ecrã 2017-03-29, às 22.22.45.png

 

Captura de ecrã 2017-03-29, às 22.35.58.png

 

thanks 

Share this post


Link to post
Share on other sites

Okay.

Q. When normal boot, read nvram.plist in ESP, now rc script make nvram.plist when reboot or shutdown. Like you mention 1, backup nvram, what means it? Remove?

 

no, just save for later.

 

Q. If remove nvram.plist in ESP until reboot or shutdown, when reboot or shutdown rc script automately make nvram.plist. no choice nvram clear. Need to disable rc script. No relate?

Yes, it's the same, so that you should do nothing *as always. 

Booting with this kext, to clean the nvram you have to use in Terminal:

nvram -c

... but this way everythings in nvram will be lost (why I suggested you to backup your nvram.plist to do this test: later you can restore your original configuration).

*Off course, you have to use the rc script since the kext has the File I/O disabled for this test.

Q. Can i check debug result? Just check nvram -p in terminal? What is NVRAM.kext's goal?

 

yes. like in a real mac

@Micky1979 - what does this kext do specifically? what do I look for ?

 

happy to test. should I presume this kext is just for a machine where one needs EmuVariable?

Really depend if you are happy with your nvram vars (but with this kext you can have additional vanilla ones), and this is anyway an emulation that does not require the emuvariable. Nothing will be written to your real nvram.

 

I need only someone helping making this working in Clover. Actually the kext apparently remove already present variables, but this is just the part 1, and I need to know if you can set what you want. part 2 will be keep bootloader settings.

 

Also this is a evaluation test.

 

P.S. only now I take the time to answer your questions.

Share this post


Link to post
Share on other sites

Hi I have a problem with OSX 10.12.4 upgrade from OSX 10.9.4:

 

Installed Sierra 10.12.4 onto an USB stick, booted into installer, installed on my OSX 10.9.4 HDD. After restart, the HDD still boots normal into OSX 10.9.4, only on the HDD is now a directory "macOS Install Data" and a ".IAProductInfo" file...   I read there should be also a .IA32Something/boot.efi, but it is not there..

 

How can I continue OSX Sierra upgrade from this point?   How can I force clover to continue the installation?

 

Thanks!

 

 

PS There also is a "Locked Files" dir in the macOS Install Data dir, containing a boot.efi and a boot.plist... But clover does not seem to see it...

Share this post


Link to post
Share on other sites

Hi I have a problem with OSX 10.12.4 upgrade from OSX 10.9.4:

 

Installed Sierra 10.12.4 onto an USB stick, booted into installer, installed on my OSX 10.9.4 HDD. After restart, the HDD still boots normal into OSX 10.9.4, only on the HDD is now a directory "macOS Install Data" and a ".IAProductInfo" file...   I read there should be also a .IA32Something/boot.efi, but it is not there..

 

How can I continue OSX Sierra upgrade from this point?   How can I force clover to continue the installation?

 

Thanks!

 

 

PS There also is a "Locked Files" dir in the macOS Install Data dir, containing a boot.efi and a boot.plist... But clover does not seem to see it...

 

give me more file list to boot upgrade in macOS Install Data folder.

Share this post


Link to post
Share on other sites

Hi I have a problem with OSX 10.12.4 upgrade from OSX 10.9.4:

 

Installed Sierra 10.12.4 onto an USB stick, booted into installer, installed on my OSX 10.9.4 HDD. After restart, the HDD still boots normal into OSX 10.9.4, only on the HDD is now a directory "macOS Install Data" and a ".IAProductInfo" file...   I read there should be also a .IA32Something/boot.efi, but it is not there..

 

How can I continue OSX Sierra upgrade from this point?   How can I force clover to continue the installation?

 

Thanks!

 

 

PS There also is a "Locked Files" dir in the macOS Install Data dir, containing a boot.efi and a boot.plist... But clover does not seem to see it...

I was upgrading my 10.9.5 to 10.12.1. The installation began from Mavericks GUI, continued through reboot and all is good.

There is no Clover's problem if you use revision compatible with Sierra.

Share this post


Link to post
Share on other sites

I was upgrading my 10.9.5 to 10.12.1. The installation began from Mavericks GUI, continued through reboot and all is good.

There is no Clover's problem if you use revision compatible with Sierra.

hello Slice.

i'm using clover r4047 tested upgrade to 10.12 and 10.12.3 from osx 10.11.6, all is OK. but upgrade 10.12.4 cant see the install entry in clover gui.

Share this post


Link to post
Share on other sites

i have the same problem , i have made a new 10.12.4 install usb with the last efi clover and when the first step is finished my hackintosh reboot and than i can't see MacOS install and so i can't finish the installation..

Share this post


Link to post
Share on other sites

no, just save for later.

 

 

Yes, it's the same, so that you should do nothing *as always. 

Booting with this kext, to clean the nvram you have to use in Terminal:

nvram -c

... but this way everythings in nvram will be lost (why I suggested you to backup your nvram.plist to do this test: later you can restore your original configuration).

*Off course, you have to use the rc script since the kext has the File I/O disabled for this test.

 

yes. like in a real mac

Really depend if you are happy with your nvram vars (but with this kext you can have additional vanilla ones), and this is anyway an emulation that does not require the emuvariable. Nothing will be written to your real nvram.

 

I need only someone helping making this working in Clover. Actually the kext apparently remove already present variables, but this is just the part 1, and I need to know if you can set what you want. part 2 will be keep bootloader settings.

 

Also this is a evaluation test.

 

P.S. only now I take the time to answer your questions.

 

 

here is result

-------------------------------
DATE: 2017-03-30 TIME: 17:04:25
-------------------------------
>> Begin Script: /etc/rc.shutdown.d/80.save_nvram_plist.local
>> End Script: /etc/rc.shutdown.d/80.save_nvram_plist.local

Supreme-MBP:~ supreme$ nvram -p
fakesmc-key-MSTS-ui8	%00
fmm-computer-name	 MacBook Pro
fakesmc-key-NATi-ui16	%00%1e
fakesmc-key-CLKT-ui32	%00%00%f0x
fakesmc-key-QENA-ui8	%01
36C28AB5-6566-4C50-9EBD-CBB920F83843:preferred-networks	%00%00%00%00%00%00%00%00%04%00%05%00%0e%00%00%00ASUS_Supreme5G%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%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%05%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%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%00%00%00%00%00%00%00%00%00%00%00 %00%00%00%94Y%0fGV/%aa%25k%a3/*%11%ea{%09N%d4%ea%80%e5*%c0^%baav%8e^i%b4s
36C28AB5-6566-4C50-9EBD-CBB920F83843:preferred-count	1
fakesmc-key-HI0N-ui8	%0f
36C28AB5-6566-4C50-9EBD-CBB920F83843:current-network	%00%00%00%00%00%00%00%00%04%00%05%00%0e%00%00%00ASUS_Supreme5G%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%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%05%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%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%00%00%00%00%00%00%00%00%00%00%00 %00%00%00%94Y%0fGV/%aa%25k%a3/*%11%ea{%09N%d4%ea%80%e5*%c0^%baav%8e^i%b4s
fakesmc-key-NATJ-ui8	%02
fakesmc-key-NTOK-ui8	%01
fakesmc-key-CLKH-{clh	%00%00p%80%00%01%19@
SystemAudioVolumeDB	%ed
fakesmc-key-MSPC-ui8	%0e
bluetoothActiveControllerInfo	z%e0%89%04%00%00%00%00P%14%ac%d1%b8%e2%a4%d0
4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14:IASCurrentInstallPhase	
SystemAudioVolume	7
backlight-level	i%05
4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14:IASInstallPhaseList	
Supreme-MBP:~ supreme$ 

post-980913-0-81746800-1490860961_thumb.png

 

above test, EmuVariableUefi-64.efi + NVRAM.kext in 10.12  + no rc script I/O + no nvram file in ESP.

 

not save brighntess value.

 

no need rc script in chameleon bootloader?

Share this post


Link to post
Share on other sites

give me more file list to boot upgrade in macOS Install Data folder.

 

Ok, here you go:

/
/macOS Install Data
/.IAProductInfo
/macOS Install Data/InstallESD.dmg
/macOS Install Data/Locked Files
/macOS Install Data/OSInstallAttr.plist
/macOS Install Data/index.sproduct
/macOS Install Data/InstallInfo.plist
/macOS Install Data/MacOSXInstaller.choiceChanges
/macOS Install Data/ia.log
/macOS Install Data/Locked Files/Boot Files
/macOS Install Data/Locked Files/MacOSXInstaller.choiceChanges
/macOS Install Data/Locked Files/OSInstallAttr.plist
/macOS Install Data/Locked Files/Boot Files/.disk_label
/macOS Install Data/Locked Files/Boot Files/.root_uuid
/macOS Install Data/Locked Files/Boot Files/boot.efi
/macOS Install Data/Locked Files/Boot Files/usr
/macOS Install Data/Locked Files/Boot Files/.disk_label.contentDetails
/macOS Install Data/Locked Files/Boot Files/PlatformSupport.plist
/macOS Install Data/Locked Files/Boot Files/com.apple.Boot.plist
/macOS Install Data/Locked Files/Boot Files/.disk_label_2x
/macOS Install Data/Locked Files/Boot Files/SystemVersion.plist
/macOS Install Data/Locked Files/Boot Files/prelinkedkernel
/macOS Install Data/Locked Files/Boot Files/usr/standalone/i386/EfiLoginUI

Clover doesn't show any additional "Continue installation.." entry. I am using v2.4 r4035. 

 

Is this maybe related to some RtVariables? I am using these:

		<key>BooterConfig</key>
		<string>0x28</string>
		<key>CsrActiveConfig</key>
		<string>0x67</string>

I selected loginui and installui booterconfig flags manually in the clover menu, but nothing changed. Maybe I need to change it permanently? But I don't know how this is bit-coded then...

I was somehow updated to 10.12.4. No additional efforts.

Look your bootlog and try to understand your fault.

 

Did you also create an installer image from 10.12.4 and did run that? Or did you combo update?

 

I was upgrading my 10.9.5 to 10.12.1. The installation began from Mavericks GUI, continued through reboot and all is good.

There is no Clover's problem if you use revision compatible with Sierra.

 

I did that successfully with 10.12.1, too, last year.

 

 

But AFAIK there was a different temp-installer file structure? I don't remember...  Also for the 10.12.1 installation, I used a MBR modified patch... Should I use that on my now used GPT partition too??

Share this post


Link to post
Share on other sites

above test, EmuVariableUefi-64.efi + NVRAM.kext in 10.12  + no rc script I/O + no nvram file in ESP.

 

*you need the rc script as I said, sorry if was not clear.

not save brighntess value.

 

I can see in your log: backlight-level    i%05

no need rc script in chameleon bootloader?

 

No. the kext dump the nvram (at every event in nvram, not just at shutdown/reboot) in ./nvram.plist /.nvram.plist, but this is apparently bad for Clover in case of logical volumes. (I can change the path if needed when the firmware is Clover or edkII). As I said I disabled the write operation for this test, that actually satisfy me  :D (thanks). To make a dump (*if does not work) maybe you should check "80.save_nvram_plist.local" if there is some condition that prevent it to dump the nvram, because otherwise should be just the same. 

Share this post


Link to post
Share on other sites

Ok, here you go:

/
/macOS Install Data
/.IAProductInfo
/macOS Install Data/InstallESD.dmg
/macOS Install Data/Locked Files
/macOS Install Data/OSInstallAttr.plist
/macOS Install Data/index.sproduct
/macOS Install Data/InstallInfo.plist
/macOS Install Data/MacOSXInstaller.choiceChanges
/macOS Install Data/ia.log
/macOS Install Data/Locked Files/Boot Files
/macOS Install Data/Locked Files/MacOSXInstaller.choiceChanges
/macOS Install Data/Locked Files/OSInstallAttr.plist
/macOS Install Data/Locked Files/Boot Files/.disk_label
/macOS Install Data/Locked Files/Boot Files/.root_uuid
/macOS Install Data/Locked Files/Boot Files/boot.efi
/macOS Install Data/Locked Files/Boot Files/usr
/macOS Install Data/Locked Files/Boot Files/.disk_label.contentDetails
/macOS Install Data/Locked Files/Boot Files/PlatformSupport.plist
/macOS Install Data/Locked Files/Boot Files/com.apple.Boot.plist
/macOS Install Data/Locked Files/Boot Files/.disk_label_2x
/macOS Install Data/Locked Files/Boot Files/SystemVersion.plist
/macOS Install Data/Locked Files/Boot Files/prelinkedkernel
/macOS Install Data/Locked Files/Boot Files/usr/standalone/i386/EfiLoginUI

Clover doesn't show any additional "Continue installation.." entry. I am using v2.4 r4035. 

 

Is this maybe related to some RtVariables? I am using these:

		<key>BooterConfig</key>
		<string>0x28</string>
		<key>CsrActiveConfig</key>
		<string>0x67</string>

I selected loginui and installui booterconfig flags manually in the clover menu, but nothing changed. Maybe I need to change it permanently? But I don't know how this is bit-coded then...

 

Did you also create an installer image from 10.12.4 and did run that? Or did you combo update?

 

 

I did that successfully with 10.12.1, too, last year.

 

 

But AFAIK there was a different temp-installer file structure? I don't remember...  Also for the 10.12.1 installation, I used a MBR modified patch... Should I use that on my now used GPT partition too??

 

 

please report

*you need the rc script as I said, sorry if was not clear.

 

I can see in your log: backlight-level    i%05

 

No. the kext dump the nvram (at every event in nvram, not just at shutdown/reboot) in ./nvram.plist , but this is apparently bad for Clover in case of logical volumes. (I can change the path if needed when the firmware is Clover or edkII). As I said I disabled the write operation for this test, that actually satisfy me  :D (thanks). To make a dump (*if does not work) maybe you should check "80.save_nvram_plist.local" if there is some condition that prevent it to dump the nvram, because otherwise should be just the same. 

 

A1. *you need the rc script as I said, sorry if was not clear.
 - i don't understand where do we need part in rc script?. rc script usually use logouthook to avoid failure case.
 - should i be disable logouthook? 
 
A2.I can see in your log: backlight-level    i%05
 - yeah but, brightness always hold middle dim after reboot.
 
A3. "the kext dump the nvram (at every event in nvram, not just at shutdown/reboot) in ./nvram.plist"
 - if we have nvram file in ESP?, i also wonder FileVault case.
 
Q. where i have to place nvram file? in root? or in ESP?, NVRAM.KEXT automately mount where has nvram file? and refresh if no mount ESP?
   i dont understand.
   
Q. i tried two method. place nvram in ESP or root. there is no effect. shown A2. 
 
I am still confused.
I understand the basic nvram creation process, but I still do not know how to use nvram.kext correctly.
 
If you have the nvram file in root, logoutook will always delete it before rebooting.
I wonder how nvram.kext can be used in this process.
 
I also compared the contents of nvram.plist, but the contents are still in the file.
 
thanks in advance.

fix.zip

Share this post


Link to post
Share on other sites

Replace files and test boot

 

나의 LG-F410S 의 Tapatalk에서 보냄

 

Uhm, replace what ? :)   Did you just compile a new clover version? Cannot find on source forge page...

Share this post


Link to post
Share on other sites

Uhm, replace what ? :) Did you just compile a new clover version? Cannot find on source forge page...

This is test version to resolve your problem. If it works, i will report it to slice

 

Please test

 

나의 LG-F410S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

This is test version to resolve your problem. If it works, i will report it to slice

 

Please test

 

나의 LG-F410S 의 Tapatalk에서 보냄

 

 

You mean in post #12648? Wasn't clear to me...

Share this post


Link to post
Share on other sites

no, just save for later.

 

 

Yes, it's the same, so that you should do nothing *as always. 

Booting with this kext, to clean the nvram you have to use in Terminal:

nvram -c

... but this way everythings in nvram will be lost (why I suggested you to backup your nvram.plist to do this test: later you can restore your original configuration).

*Off course, you have to use the rc script since the kext has the File I/O disabled for this test.

 

yes. like in a real mac

Really depend if you are happy with your nvram vars (but with this kext you can have additional vanilla ones), and this is anyway an emulation that does not require the emuvariable. Nothing will be written to your real nvram.

 

I need only someone helping making this working in Clover. Actually the kext apparently remove already present variables, but this is just the part 1, and I need to know if you can set what you want. part 2 will be keep bootloader settings.

 

Also this is a evaluation test.

 

P.S. only now I take the time to answer your questions.

 

@Micky1979 -

 

so i installed FileNRAM.kext and my T460 UEFI system (non-legacy) can now boot with or without EmuVariable-64.efi

 

but it removed all the other NVRAN variables? what's that all about? 

these are the only values that are there now upon boot up:

$ nvram -p |sort| awk '{print $1}'
36C28AB5-6566-4C50-9EBD-CBB920F83843:current-network
36C28AB5-6566-4C50-9EBD-CBB920F83843:preferred-count
36C28AB5-6566-4C50-9EBD-CBB920F83843:preferred-networks
4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14:IASCurrentInstallPhase
4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14:IASInstallPhaseList
LocationServicesEnabled
SystemAudioVolume
SystemAudioVolumeDB
backlight-level
bluetoothActiveControllerInfo
fmm-computer-name

where does the kext expect to save and/or read (restore) any persisted values ?

 

Note: using the current nvram save scripts, the OS root ( /nvram.plist) file would be deleted on  system that using /Volume/ESP to store the persisted  nvram.plist

 

doesn't Clover need some of these variables before the OS boots up?

 

So it seems we still need EmuVariable to provide NVRAM support before OS boot. Your kext provides NVRAM support after OS boot, if  I understand this whole thing?!

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   0 members

    No registered users viewing this page.

  • Similar Content

    • By ErmaC
      Slice is glad to present a new EFI bootloader.

      CLOVER
      Now version 2 rEFIt based.


      It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision.
      I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources.
      https://sourceforge.net/projects/cloverefiboot/?source=directory
      There is a WIKI 
      http://clover-wiki.zetam.org/
      Main features:


      If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma!
      Continued by blackosx and STLVNUB.
      Post#2 CloverGrower - create Clover by yourself Post#3 Downloads Post#4 Installation of the bootloader Post#5 How to do UEFI boot Post#6 How to use - common words Post#7 Calculator for Automatic DSDT fix Post#8 Instructions for GraphicsInjector Post#9 ATIConnector patching Post#10 Any kexts patching with some Samples Post#11 CustomEDID Post#12 Hiding unnecessary menu entries Post#13 Instruction for DSDT corrections to do DeviceInjection works Post#14 Development Post#15 Themes Post#16 About kexts injection Post#17 Instructions for P- and C-states generator Post#18 Patching DSDT to get Sleep working Post#19 CPU settings and geekbench Post#20 ACPI tables loading Post#21 DSDTmini Post#22 Custom SMBios Post#23 F.A.Q. Post#24 iCloudFix Post#25 Using mouse. Post#26 How to make orange icons to be metallic Post#27 How to make software RAID (by Magnifico) Post#28 How to modify InstallESD.dmg (by shiecldk) Post#29 Config.plist settings Post#30 Using extra kexts and skipping kernelcache Post#31 Choosing EFI drivers Post#32 Configuration files Post#33 Automatic config.plist creating Post#34 Custom DSDT patches Post#35 How to do sleep/wake working with UEFI BOOT Post#36 DeviceID substitution (FakeID) Post#37 Using Custom OS Icons Post#38 Hibernation Post#39 Floating regions Post#41 Property List Editor Post#42 Blocking Bad Kext Post#43 AAPL,slot-name Post#44 FakeCPUID for unsupported CPU Post#45 Multiple Boot Options - to write into UEFI BIOS boot menu Post#46 How to install Windows UEFI Post#47 How to speedup Clover boot Post#48 Info.plist patching Post#49 Arbitrary device injection Post#50 Non-Standard Legacy Boot Files Post#51 Reboot to Windows UEFI from Mac OSX Post#52 Deprecated Features Post#53 Using UDK2018 Post#54 Device Properties Post#55 Scalable themes Post#56 How to search Clover mistakes (bisection) -----------------
       
      Slice:
      I edited all posts in the thread to correspond to actual Clover revision.
      Please install Clover at least 2652 and use new instructions.
×