Jump to content

d620osx

Members
  • Content Count

    283
  • Joined

  • Last visited


Reputation Activity

  1. Like
    d620osx reacted to Slice in Cannot see APFS partition   
    Sierra is not working with APFS. It is for HighSierra and up.
  2. Like
    d620osx reacted to Jief_Machak in Clover General discussion   
    I think it's at least 5101.
  3. Like
    d620osx reacted to Jief_Machak in Clover General discussion   
    I don't think you should put a # in front. If I remember well, the # was to hide that information. You have to have a very recent Clover to see that information.
    If you don't have a file called .VolumeLabel.txt, you still should see something like Clover booted from EFI. If not, your CLover is too old.
  4. Like
    d620osx reacted to Jief_Machak in Clover General discussion   
    Put a .VolumeLabel.txt file in all your partitions in all your hard drives and USB sticks (or at least on all your partitions containing Clover). In this file, put a name like 'EFI on 1TB SDD' or 'HighSierra on Samsung' etc.
    Then, at bottom right, you'll see Clover booted from xxx.
  5. Like
    d620osx reacted to vector sigma in Clover General discussion   
    Then, I'm almost conviced that you are booting from the wrong partition.... 
  6. Like
    d620osx reacted to Slice in Clover General discussion   
    Use Clover.app
    https://github.com/CloverHackyColor/CloverBootloader/releases
  7. Like
    d620osx reacted to chris1111 in [Guide] macOS High Sierra 10.13 - Dell Optiplex 780 (760) (755) (790) (990)   
    Use this config, its adapted for Catalina and works for ancient macOS
    config.plist.zip
     
    This is strange the user does not come back after he has had what he asked for 
  8. Like
    d620osx reacted to Sherlocks in Clover.app testing   
    sometimes added apple weekly report schedule in pmset.

    in my system, both laptop and desktop don't have a issue

    나의 SM-N960N 의 Tapatalk에서 보냄

  9. Like
    d620osx got a reaction from vector sigma in Clover.app testing   
    Wake on Network is already switched off, I have also tried unplugging all the usb items apart from the keyboard and no joy. For some reason it only happens during the night.
     
    Will keep investigating, thank you for all  your help.
  10. Like
    d620osx reacted to vector sigma in Clover.app testing   
    After disabling the mdns responder service your problem is else were. May be you should uncheck the "Wake Wifi (or whatever) network access" in the save energy saver panel?
    you should try the new v1.1.0 instead of the 1.0.9. The UI problem was fixed 3 days ago here
  11. Like
    d620osx reacted to Sherlocks in Clover.app testing   
    report of 1.0.4
    CloverDaemonNew is not working.
    1.0.3 is no problem.
     
    1.0.4


     
    there is no part "- CloverDaemonNew v1.0.9"
     
    1.0.3


     
    Also ui bug
    closed clover app 
    and open it again. then first ui shown selected theme part. but contents actually show disk part.

  12. Like
    d620osx reacted to vector sigma in Clover.app testing   
    Thanks!
    EDIT
    committed
    Yes, now it is really good:
    -------------------------------------------- - CloverDaemonNew v1.0.9 - macOS Version 10.15.1 (Build 19B88) - System start at 2020-01-02 05:37:01 ------ root mount point is '/Volumes/SSD_CATALINA' Started with Clover r5097. Firmware vendor is 'CLOVER'. making '/' writable as Clover.RootRW=true. Clover.DisableSleepProxyClient=true. Sleep Proxy Client is already disabled. Installing the LogoutHook.. LogoutHook is already set. Logout hook is: /Library/Application Support/Clover/CloverLogOut SIGTERM received at 2020-01-02 05:37:17 Clover.DisableSleepProxyClient=true. Sleep Proxy Client is already disabled.  
    It is an Application and not a kernel extension, so I don't understand what cache you want delete. There is no cache.
  13. Thanks
    d620osx got a reaction from vector sigma in Clover.app testing   
    Hi @vector sigma,
     
    Happy New Year and thank you for the updated app. I have run this and have attached an updated log. From my limited knowledge I presume the last fix you have applied has fixed the issues on my machine and waking from sleep will be resolved.
     
    Will keep an eye and report back.
     
    Thank you again for all your time and help.
    clover.daemon.log
  14. Like
    d620osx reacted to vector sigma in Clover.app testing   
    Happy new year to all!!!
  15. Like
    d620osx reacted to vector sigma in Clover.app testing   
    Clover.app v1.13 with Clover r5102:
     
    Fixed detection of legacy firmware for CloverDaemonNew. Detection of System Serial and OEM manufacturer informations. Startup sound settings in the interface. Installer inform with a sound and an alert window the installation result. Installer now produce the installation log. Installer is now thread safe. The UI is modified to make room for all the new functionalities  
    that is how the UI looks like now:
     
      
    the installer button is moved down, under "Update":

    ...as it fit better.. 
    Let me know.
  16. Like
    d620osx reacted to vector sigma in Clover.app testing   
    Not sure, all other are fine, may be also an upload problem. Anyway today 1.13 will be ready with the sound settings ability and more.
  17. Like
    d620osx reacted to vector sigma in Clover.app testing   
    For the moment run this in Terminal:
    sudo nvram TestEmuVariableUefiPresent=true Then I'll change how to recognize a legacy boot
  18. Like
    d620osx reacted to Slice in Clover.app testing   
    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.
  19. Like
    d620osx reacted to vector sigma in Clover.app testing   
    How to know then when the system is loaded from the bios? From the firmware name?
  20. Like
    d620osx reacted to Slice in Clover.app testing   
    Yes, it will be CLOVER.
    UEFI boot looks like

  21. Like
    d620osx reacted to vector sigma in Clover.app testing   
    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.
  22. Like
    d620osx got a reaction from vector sigma in Clover.app testing   
    Thank you Sir for your help. Enjoy your shopping.

    Sent from my Moto G (5) using Tapatalk

  23. Like
    d620osx reacted to vector sigma in Clover.app testing   
    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..
  24. Like
    d620osx reacted to vector sigma in Clover.app testing   
    Yep, that was implicit Lol. Please do that (as well for "make filesystem RW"), reboot twice and post the log, thanks.
  25. Like
    d620osx reacted to Sherlocks in Clover.app testing   
    seem you are not install rc script or newcloverdaemon of clover app.
    PutNvramPlistToRtVars: nvram.plist not found you need to check nvram.plist on ESP.
×