Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,858 posts in this topic

Recommended Posts

Funky frank
Funky frank
Posted
Posted

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...

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

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.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

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.

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

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.

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

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?

Link to comment
Share on other sites
Funky frank
Funky frank
Posted
Posted

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

Link to comment
Share on other sites
Micky1979
Micky1979
Posted
Posted

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. 

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

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

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

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

Link to comment
Share on other sites
tluck
tluck
Posted
Posted

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

Link to comment
Share on other sites
Funky frank
Funky frank
Posted
Posted

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

 

Please test

 

나의 LG-F410S 의 Tapatalk에서 보냄

 

Installed the version from post #12648 now, but clover still does not show any additional install drive/option...

Link to comment
Share on other sites
juanerson
juanerson
Posted
Posted

Hi guys, clover do something strange by adding ".metadata_never_index" (+ nvram.plist) to my system root folder. Which prevent Spotlight to work.

 

Legacy system PC running Yosemite 10.10.5 with clover r.4035

Clover installed on EFI partition.

Full GPT (not hybrid MBR) dual boot with windows 10 (UEFI boot = bootmgfw.efi)

 

Please, if you need more info tell me. Thank You.

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Hi guys, clover do something strange by adding ".metadata_never_index" (+ nvram.plist) to my system root folder. Which prevent Spotlight to work.

 

Legacy system PC running Yosemite 10.10.5 with clover r.4035

Clover installed on EFI partition.

Full GPT (not hybrid MBR) dual boot with windows 10 (UEFI boot = bootmgfw.efi)

 

Please, if you need more info tell me. Thank You.

 

in terminal

 

sudo cat /Library/Logs/CloverEFI/rc.shutdown.log

 

when you get nvram.plist in root

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

Thank you, Sherlocks. Output:

attachicon.gifCaptura de pantalla 2017-03-30 a las 8.38.54.png

Then, I erased the two files from the root:

sudo rm /.metadata_never_index

sudo rm /nvram.plist

 

But, at next reboot them appeared again in root. Please, how to fix it?

Your system has old rc script. Please update clover build if you can build. Now, rc script version is 1.16.2

 

나의 LG-F410S 의 Tapatalk에서 보냄

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

@tluck, @Sherlocks, thanks to had taken the time to test it. I tried to explain that this was only a test and that the kext does not write nothing by it-self (is capable, but disabled in code)... Also the reason why I said that to dump the nvram you need the rc scripts for that (since how to dump the contents of the /options node is really unrilevant to me now). In UEFI this is not possible unless you remove the check for the firmware name and/or for emuvariable present, why I asked to test with Clover EFI.

 

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.


the test is succesfull for me (in a big part) at least looking at Sherlocks dump here since you can see FakeSMC keys + all other GUIDs discovered by FileNVRAM (but there is a long list of variables processed taken from your IO). 
I was not expected you to completely switch on it, just a test, and thanks :)

I'll open a new Topic for developments if any.

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

is clover updated with the new 10.12.4 installer kernel? it looks like some users cant boot to it. or EFIPlus.efi driver issue?

- First attempt to upgrade an existing installation of El Capitan to Sierra unsing "Install macOS Sierra.app": failure

   Rebooting to the OS I cannot find the prelinkedkernel and the com.apple.boot.plist inside generated directories: the official app has clearly failed to correctly create the installer.

- Second attempt with the app: all ok, and Clover (with no surprise) boot into the installer gui. :)

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