d620osx Posted December 24, 2019 Share Posted December 24, 2019 3 minutes ago, vector sigma said: nothing else, let see. But may be better that you do two reboots to see if the daemon installed the correct logout hook as we will see that only on the second one. Thank you, second re-boot also done. Do I need to re-run the DisableSleepProxyClient from the clover app or just see if the hack wakes up again tonight? Link to comment Share on other sites More sharing options...
vector sigma Posted December 24, 2019 Author Share Posted December 24, 2019 4 minutes ago, d620osx said: Do I need to re-run the DisableSleepProxyClient from the clover app Yep, that was implicit Lol. Please do that (as well for "make filesystem RW"), reboot twice and post the log, thanks. 1 Link to comment Share on other sites More sharing options...
d620osx Posted December 24, 2019 Share Posted December 24, 2019 Looks like I may be doing something wrong. I have tickled both boxes, selected Install on Clover Daemon and re-booted twice. Log attached. Thank you clover.daemon.log Link to comment Share on other sites More sharing options...
vector sigma Posted December 24, 2019 Author Share Posted December 24, 2019 2 minutes ago, d620osx said: Looks like I may be doing something wrong. I have tickled both boxes, selected Install on Clover Daemon and re-booted twice. Log attached. Thank you clover.daemon.log yep, looks like the old logout hook resist to the Terminal too lol. Please run this in Terminal: sudo defaults write com.apple.loginwindow LoginHook /Library/Application\ Support/Clover/CloverLogOut reboot twice and reply with the log again. That must work, I guess. @d620osx, I didn't ask, but I guess you already installed EmuVariableUefi.efi, right? Link to comment Share on other sites More sharing options...
d620osx Posted December 24, 2019 Share Posted December 24, 2019 (edited) 9 minutes ago, vector sigma said: yep, looks like the old logout hook resist to the Terminal too lol. Please run this in Terminal: sudo defaults write com.apple.loginwindow LoginHook /Library/Application\ Support/Clover/CloverLogOut reboot twice and reply with the log again. That must work, I guess. @d620osx, I didn't ask, but I guess you already installed EmuVariableUefi.efi, right? Just checked EFI > DRIVERS > BIOS > UEFI and I do have EmuVariableUefi.efi. The log does say that it is missing. Thank you clover.daemon.log Edited December 24, 2019 by d620osx Link to comment Share on other sites More sharing options...
vector sigma Posted December 24, 2019 Author Share Posted December 24, 2019 (edited) 20 minutes ago, d620osx said: Just checked EFI > DRIVERS > BIOS > UEFI and I do have EmuVariableUefi.efi. The log does say that it is missing. Thank you clover.daemon.log The log just wanted to say that EmuVariableUefiPresent is not present. It is a variable that Clover should put in NVRAM so the daemon should know when save to nvram.plist. But the problem here is another: Logout hook is: /Library/Application Support/Clover/CloverDaemon-stopservice that means that rcscripts are there, up and running, when they should be removed. That is the probem. Now I have to go buy to two more gifts....I'll be back later.. Edited December 24, 2019 by vector sigma typos 1 Link to comment Share on other sites More sharing options...
d620osx Posted December 24, 2019 Share Posted December 24, 2019 The log just wanted to say that EmuVariableUefiPresent is not present. It is a variable that Clover should put in NVRAM so the daemon should know when save to nvram.plist. But the problem here is another:Logout hook is: /Library/Application Support/Clover/CloverDaemon-stopservice that means that rcscripts are there, up and running, when they should be removed. That is the probem. Now I have to go buy to more gifts....I'll be back later..Thank you Sir for your help. Enjoy your shopping. Sent from my Moto G (5) using Tapatalk 1 Link to comment Share on other sites More sharing options...
D-an-W Posted December 24, 2019 Share Posted December 24, 2019 This is my daemon log after a couple of reboots. I don't have any files in either rc.boot.d or rc.shutdown.d but it still refers to them, should I perhaps clean my NVRAM? --------------------------------------------------- CloverDaemon start at 2019-12-24 20:14:46 --------------------------------------------------- 2019-12-24 20:14:47 - All clover startup scripts (locate in /private/etc/rc.boot.d) have been started --------------------------------------------------- CloverDaemon start at 2019-12-24 20:19:28 --------------------------------------------------- 2019-12-24 20:19:28 - All clover startup scripts (locate in /private/etc/rc.boot.d) have been started -------------------------------------------- - CloverDaemonNew v1.0.8 - macOS Version 10.15.3 (Build 19D49f) - System start at 2019-12-24 08:20:26 ------ root mount point is '/Volumes/Macintosh HD' Started with Clover r5101. Clover.DisableSleepProxyClient is not set. Sleep Proxy Client is already enabled as default. Clover.MountEFI=5BA6920C-B73F-46C4-9E37-AF687CAE5B25 try to mount disk0s1 as requested. Logout hook is: /etc/rc.shutdown.d/80.save_nvram_plist.local SIGTERM received at 2019-12-24 08:34:00 Clover.DisableSleepProxyClient is not set. Sleep Proxy Client is already enabled as default. 1 Link to comment Share on other sites More sharing options...
Beajar Posted December 27, 2019 Share Posted December 27, 2019 good grief. The Clover 5101 installer was so fast it seemed like nothing happened so I ran it again. Thanks!! 1 Link to comment Share on other sites More sharing options...
vector sigma Posted December 27, 2019 Author Share Posted December 27, 2019 11 hours ago, Beajar said: good grief. The Clover 5101 installer was so fast it seemed like nothing happened so I ran it again. Thanks!! Ok, I'll make it show an alert window when it done.. On 12/24/2019 at 9:41 PM, D-an-W said: This is my daemon log after a couple of reboots. I don't have any files in either rc.boot.d or rc.shutdown.d but it still refers to them, should I perhaps clean my NVRAM? --------------------------------------------------- CloverDaemon start at 2019-12-24 20:14:46 --------------------------------------------------- 2019-12-24 20:14:47 - All clover startup scripts (locate in /private/etc/rc.boot.d) have been started --------------------------------------------------- CloverDaemon start at 2019-12-24 20:19:28 --------------------------------------------------- 2019-12-24 20:19:28 - All clover startup scripts (locate in /private/etc/rc.boot.d) have been started -------------------------------------------- - CloverDaemonNew v1.0.8 - macOS Version 10.15.3 (Build 19D49f) - System start at 2019-12-24 08:20:26 ------ root mount point is '/Volumes/Macintosh HD' Started with Clover r5101. Clover.DisableSleepProxyClient is not set. Sleep Proxy Client is already enabled as default. Clover.MountEFI=5BA6920C-B73F-46C4-9E37-AF687CAE5B25 try to mount disk0s1 as requested. Logout hook is: /etc/rc.shutdown.d/80.save_nvram_plist.local SIGTERM received at 2019-12-24 08:34:00 Clover.DisableSleepProxyClient is not set. Sleep Proxy Client is already enabled as default. Your looks good, but looks like you're running in UEFI? isn't? Link to comment Share on other sites More sharing options...
vector sigma Posted December 27, 2019 Author Share Posted December 27, 2019 (edited) On 12/24/2019 at 4:20 PM, vector sigma said: yep, looks like the old logout hook resist to the Terminal too lol. Please run this in Terminal: sudo defaults write com.apple.loginwindow LoginHook /Library/Application\ Support/Clover/CloverLogOut reboot twice and reply with the log again. That must work, I guess. @d620osx, I didn't ask, but I guess you already installed EmuVariableUefi.efi, right? Sir I made a mistake, sorry. The above command you run is it for login and not for logout (LoginHook instead of LogoutHook). Please run the following to fix it: sudo defaults delete com.apple.loginwindow LoginHook then, if you want continue try, please run the correct command: sudo defaults write com.apple.loginwindow LogoutHook /Library/Application\ Support/Clover/CloverLogOut I'm making changes on the installation process of the Daemon because actually the logout hook is installed by him at start up, while later the logout will be installed by the app, during the installation of the daemon. This is to have an nvram.plist just before the first power off. Edited December 27, 2019 by vector sigma 2 Link to comment Share on other sites More sharing options...
D-an-W Posted December 27, 2019 Share Posted December 27, 2019 59 minutes ago, vector sigma said: Ok, I'll make it show an alert window when it done.. Your looks good, but looks like you're running in UEFI? isn't? Hi @vector sigma, I installed a new SSD so did a fresh install and here is how it looks now... -------------------------------------------- - CloverDaemonNew v1.0.8 - macOS Version 10.15.2 (Build 19C57) - System start at 2019-12-25 10:51:20 ------ root mount point is '/Volumes/Macintosh HD' Started with Clover r5101. Clover.DisableSleepProxyClient is not set. Cannot go ahead as / is read-only Clover.MountEFI=C06B6654-5FDE-456F-B2E3-041B3ABDBDC2 try to mount disk0s1 as requested. Logout hook is: none SIGTERM received at 2019-12-25 10:52:50 Clover.DisableSleepProxyClient is not set. Cannot go ahead as / is read-only -------------------------------------------- - CloverDaemonNew v1.0.8 - macOS Version 10.15.2 (Build 19C57) - System start at 2019-12-25 10:53:40 ------ root mount point is '/Volumes/Macintosh HD' Started with Clover r5101. Clover.DisableSleepProxyClient is not set. Cannot go ahead as / is read-only Clover.MountEFI=C06B6654-5FDE-456F-B2E3-041B3ABDBDC2 try to mount disk0s1 as requested. Logout hook is: none SIGTERM received at 2019-12-26 09:00:06 Clover.DisableSleepProxyClient is not set. Cannot go ahead as / is read-only Link to comment Share on other sites More sharing options...
vector sigma Posted December 27, 2019 Author Share Posted December 27, 2019 (edited) Yes it is ok. In this new one says: Logout hook is: none And it is fine because you never install the rcscripts nor the new Daemon installed the logouthook. The old one instead show: Logout hook is: /etc/rc.shutdown.d/80.save_nvram_plist.local and is fine too because you previously installed the rc scripts, but the daemon didn't remove it from com.apple.loginwindow.plist because EmuVariableUefiPresent did not exist in NVRAM. this means your're running in UEFI... Isn't? Edited December 27, 2019 by vector sigma typo Link to comment Share on other sites More sharing options...
D-an-W Posted December 27, 2019 Share Posted December 27, 2019 Yes, its a UEFI install. Am I right in saying that it will only notify about new versions when the number changes (5101 > 5102) and if I want the incremental stuff I should build a new version of the .app and install from there? Link to comment Share on other sites More sharing options...
d620osx Posted December 27, 2019 Share Posted December 27, 2019 2 hours ago, vector sigma said: Sir I made a mistake, sorry. The above command you run is it for login and not for logout (LoginHook instead of LogoutHook). Please run the following to fix it: sudo defaults delete com.apple.loginwindow LoginHook then, if you want continue try, please run the correct command: sudo defaults write com.apple.loginwindow LogoutHook /Library/Application\ Support/Clover/CloverLogOut I'm making changes on the installation process of the Daemon because actually the logout hook is installed by him at start up, while later the logout will be installed by the app, during the installation of the daemon. This is to have an nvram.plist just before the first power off. Hi @vector sigma, No need to say sorry Sir, I am grateful for the app and the help you giving me to sort out the sleep issues. I have run both commands in terminal and have attached the log. Do you need me to re-run both the disable sleep and re-write scripts? Thank you clover.daemon.log Link to comment Share on other sites More sharing options...
telepati Posted December 27, 2019 Share Posted December 27, 2019 (edited) @vector sigma I am totally confused about NVRAM. My motherboard is Z390 series and as far as I know, this series board does not support native NVRAM. I normally used AptioMemoryFix.efi but lately I am starting to get allocate error on boot. (I also tried all AptioFix EFI's inside the clover none of them worked). And I decided to use OcQuirks + FwRuntimeServices.efi looks everything working now. But the OcQuirks demands the EmuvariableUefi.efi other hand EmuvariableUefi demands the RcScript. I installed CloverDaemonNew from your app am I still need RcScript? Also, how can I test my NVRAM is working properly? Edited December 27, 2019 by telepati 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted December 27, 2019 Share Posted December 27, 2019 25 minutes ago, telepati said: @vector sigma I am totally confused about NVRAM. My motherboard is Z390 series and as far as I know, this series board does not support native NVRAM. I normally used AptioMemoryFix.efi but lately I am starting to get allocate error on boot. (I also tried all AptioFix EFI's inside the clover none of them worked). And I decided to use OcQuirks + FwRuntimeServices.efi looks everything working now. But the OcQuirks demands the EmuvariableUefi.efi other hand EmuvariableUefi demands the RcScript. I installed CloverDaemonNew from your app am I still need RcScript? Also, how can I test my NVRAM is working properly? CloverDaemonNew is a complete replacement for the RC Scripts (Page 1 of this topic). Tell me in MP, if you find a solution. 1 Link to comment Share on other sites More sharing options...
vector sigma Posted December 27, 2019 Author Share Posted December 27, 2019 (edited) 3 hours ago, d620osx said: Hi @vector sigma, No need to say sorry Sir, I am grateful for the app and the help you giving me to sort out the sleep issues. I have run both commands in terminal and have attached the log. Do you need me to re-run both the disable sleep and re-write scripts? Thank you clover.daemon.log Ok now logout hook is it working and I can see progress: - CloverLogOut v1.0.3: logout begin at 2019-12-24 03:34:55 EmuVariableUefi is not present, nvram will not be saved. - CloverLogOut: end at 2019-12-24 03:34:55 - CloverLogOut v1.0.3: logout begin at 2019-12-26 08:52:18 EmuVariableUefi is not present, nvram will not be saved. - CloverLogOut: end at 2019-12-26 08:52:18 It state that He can't found the EmuVariableUefiPresent variable (means that EmuVariableUefi.efi is not loaded or not installed), so It wont save the nvram. Can you post your entire EFI directory after removing any serial you may have from the config.plist? thanks in advance. Until EmuVariableUefiPresent is not present in the emulated nvram, there no will be chances that the CloverDaemonNew (nor the RC scripts) will save the nvram because it think you're running with native nvram. Edited December 27, 2019 by vector sigma 1 Link to comment Share on other sites More sharing options...
vector sigma Posted December 27, 2019 Author Share Posted December 27, 2019 (edited) 1 hour ago, telepati said: Also, how can I test my NVRAM is working properly? Ok, run in Terminal the following: sudo nvram telepati=hi reboot. After the reboot open again the Terminal and type: nvram telepati if the NVRAM is working it will show you: telepati hi if not working it will tells you something like that: nvram: Error getting variable - 'telepati': (iokit/common) data was not found Edited December 27, 2019 by vector sigma 1 1 Link to comment Share on other sites More sharing options...
vector sigma Posted December 27, 2019 Author Share Posted December 27, 2019 (edited) 3 hours ago, D-an-W said: Yes, its a UEFI install. Am I right in saying that it will only notify about new versions when the number changes (5101 > 5102) and if I want the incremental stuff I should build a new version of the .app and install from there? No, when it show a new version in the top bar is because you have an old version installed (e.g. in the ESP) or because the app has an old version embedded. Then Clover.app should show you when a new version of the app is available. That based on the intervall you chose (daily,weekly, montly). Edited December 27, 2019 by vector sigma Link to comment Share on other sites More sharing options...
d620osx Posted December 27, 2019 Share Posted December 27, 2019 3 hours ago, vector sigma said: Ok now logout hook is it working and I can see progress: - CloverLogOut v1.0.3: logout begin at 2019-12-24 03:34:55 EmuVariableUefi is not present, nvram will not be saved. - CloverLogOut: end at 2019-12-24 03:34:55 - CloverLogOut v1.0.3: logout begin at 2019-12-26 08:52:18 EmuVariableUefi is not present, nvram will not be saved. - CloverLogOut: end at 2019-12-26 08:52:18 It state that He can't found the EmuVariableUefiPresent variable (means that EmuVariableUefi.efi is not loaded or not installed), so It wont save the nvram. Can you post your entire EFI directory after removing any serial you may have from the config.plist? thanks in advance. Until EmuVariableUefiPresent is not present in the emulated nvram, there no will be chances that the CloverDaemonNew (nor the RC scripts) will save the nvram because it think you're running with native nvram. Sorry for some reason the efi folder is over 10mb, so I have zipped only the clover folder. Under the other folder I have BOOT > BOOTX64.EFI and /Volumes/EFI/EFI/APPLE/EXTENSIONS/Firmware.scap /Volumes/EFI/EFI/APPLE/UPDATERS/MULTIUPDATER files as per the attached. Thank you for your help. CLOVER.zip Link to comment Share on other sites More sharing options...
vector sigma Posted December 28, 2019 Author Share Posted December 28, 2019 (edited) 6 hours ago, d620osx said: Sorry for some reason the efi folder is over 10mb, so I have zipped only the clover folder. Under the other folder I have BOOT > BOOTX64.EFI and /Volumes/EFI/EFI/APPLE/EXTENSIONS/Firmware.scap /Volumes/EFI/EFI/APPLE/UPDATERS/MULTIUPDATER files as per the attached. Thank you for your help. CLOVER.zip For the moment run this in Terminal: sudo nvram TestEmuVariableUefiPresent=true Then I'll change how to recognize a legacy boot Edited December 28, 2019 by vector sigma need a fix 2 Link to comment Share on other sites More sharing options...
Slice Posted December 28, 2019 Share Posted December 28, 2019 No, in legacy boot, BIOS mode, there is own embedded EmuVariableDxe. For UEFI boot the is EmuVariableUefi.efi Variable EmuVariableUefiPresent is not present in legacy boot. 2 Link to comment Share on other sites More sharing options...
vector sigma Posted December 28, 2019 Author Share Posted December 28, 2019 4 minutes ago, Slice said: Variable EmuVariableUefiPresent is not present in legacy boot. How to know then when the system is loaded from the bios? From the firmware name? 1 Link to comment Share on other sites More sharing options...
Slice Posted December 28, 2019 Share Posted December 28, 2019 2 hours ago, vector sigma said: How to know then when the system is loaded from the bios? From the firmware name? Yes, it will be CLOVER. UEFI boot looks like 2 Link to comment Share on other sites More sharing options...
Recommended Posts