Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

smolderas
smolderas
Posted
Posted

@Sherlocks

It also needs com.projectosx.clover.daemon.plist in /Library/Application Support/LaunchDaemons (which must be activated with launchctl), aswell as /etc/rc.clover.lib ! Although I didn't test the newest version...

And /Library/Application Support/Clover/CloverDaemon is needed.

The newest version didn't change that mechanism. The following is not necessary if the script got installed from the clover installer.

 

One can place a logouthook though:

sudo defaults write com.apple.loginwindow LogoutHook /etc/rc.shutdown.d/80.save_nvram_plist.local
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

@Sherlocks

It also needs com.projectosx.clover.daemon.plist in /Library/Application Support/LaunchDaemons (which must be activated with launchctl), aswell as /etc/rc.clover.lib ! Although I didn't test the newest version...

And /Library/Application Support/Clover/CloverDaemon is needed.

 

i tested official r3961 build. not properly work nvram.

 

i builded r3960. and tested it. no problem.

 

i tested all full pkg install.

Link to comment
Share on other sites
smolderas
smolderas
Posted
Posted

nvram brightness save test

 

summary

r3960 : work

r3961 : not work

your new script : not work

 

your script always hold brightness 100% after boot

The new script saves in your root partition, as you posted before. There must be somewhere else another nvram.plist, who got read from clover.

Can you find it and delete it?

Maybe look for `bdmesg|grep nvram.plist` where it got loaded.

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

The new script saves in your root partition, as you posted before. There must be somewhere else another nvram.plist, who got read from clover.

Can you find it and delete it?

Maybe look for `bdmesg|grep nvram.plist` where it got loaded.

 

here

Last login: Thu Dec 15 01:12:28 on console

Supreme-MBP:~ supreme$ bdmesg|grep nvram.plist

0:390  0:000  Loading nvram.plist from Vol 'Macintosh SSD' - loaded, size=3718

 

Supreme-MBP:~ supreme$ 

 

i have only nvram file in root.

 

already tested remove and see result. but still not success.

The new script saves in your root partition, as you posted before. There must be somewhere else another nvram.plist, who got read from clover.

Can you find it and delete it?

Maybe look for `bdmesg|grep nvram.plist` where it got loaded.

 

 

my steps for test

1. install clover from 3961 full pkg

2. test brightness, etc, nvram is not work properly. 

 

i downloaded old script from r3960 repo. and like you said, i did terminal command.

 

it's work. as result, your script has something wrong.

Link to comment
Share on other sites
smolderas
smolderas
Posted
Posted

here

Last login: Thu Dec 15 01:12:28 on console

Supreme-MBP:~ supreme$ bdmesg|grep nvram.plist

0:390  0:000  Loading nvram.plist from Vol 'Macintosh SSD' - loaded, size=3718

 

Supreme-MBP:~ supreme$ 

 

i have only nvram file in root.

 

already tested remove and see result. but still not success.

 

 

my steps for test

1. install clover from 3961 full pkg

2. test brightness, etc, nvram is not work properly. 

 

i downloaded old script from r3960 repo. and like you said, i did terminal command.

 

it's work. as result, your script has something wrong.

I'm assuming you have first tested with the newest script (with LogoutHook as well?)...

 

I don't want to force anybody to use it, but it is needed for FileVault 2 and I'm more then willing to fix this issue. You are free to use the old one. But I like to debug it with you.

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

I'm assuming you have first tested with the newest script (with LogoutHook as well?)...

 

I don't want to force anybody to use it, but it is needed for FileVault 2 and I'm more then willing to fix this issue. You are free to use the old one. But I like to debug it with you.

Latest clover has your script. It needs to fix this issue.

 

I'm in late time.

So if you attached some files, i will give you information and report after i wake up or have free time.

 

 

 

나의 LG-F410S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
PMheart
PMheart
Posted
Posted

 

Could you please post the result of the following:

diskutil list

I don't see any issue for having an EFI partition. I even think if you ever try to repair your disk in macOS, it will ensure that an EFI partition exists.

 

Whatever the case maybe for not having an EFI partition, I'll post soon a newer version of the script with a fallback to the root partition, if there is no EFI partition. With that it should work for everybody (I think).

 

Sorry for any inconvenience.

 

Edit: Here is the script with the fallback to the root partition. For everyone else just copy it to its location and change its executable bit:

sudo cp ~/Downloads/80.save_nvram_plist.local.txt /etc/rc.shutdown.d/80.save_nvram_plist.local
sudo chmod 755 /etc/rc.shutdown.d/80.save_nvram_plist.local

If you don't have ESP then it's impossible to do anything here..

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Actually the updated script saves to root partition of the boot volume as fallback, if it can't find or save to the ESP.

Did you test it?

 

Edit: I mean not the script from r3961, but from post #11942

 

i found wrong code.

this is

 

function saveNVRAM {

    local rootDevice=$(LC_ALL=C diskutil info /|awk '{ if ($1 == "Device" && $2 == "Node:") {print $3}}' | sed -nE 's#^/dev/([^ ]*).*#\1#p')
 

 

it cause to not properly work nvram save after reboot.

 

i returned this code from old script.

 

    local rootDevice=$(df -l / | sed -nE 's#^/dev/([^ ]*).*#\1#p')

 

i checked it. brightness and other values are working.

 

you find solution to fix this issue from this hint.

 

i edited your latest script in dropbox.

 

Last login: Thu Dec 15 11:36:38 on console

Supreme-MBP:~ supreme$ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local

Password:

NVRAM saved to '/nvram.plist' [disk0s4]

Supreme-MBP:~ supreme$ sudo nvram myvar="this is a new variable"

Supreme-MBP:~ supreme$ nvram -p|grep myvar

myvar this is a new variable

Supreme-MBP:~ supreme$ bdmesg|grep nvram.plist

0:389  0:000  Loading nvram.plist from Vol 'Macintosh SSD' - loaded, size=7257

Supreme-MBP:~ supreme$ 

 

thank you.

80.save_nvram_plist.local.zip

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

i found wrong code.

this is

 

it cause to not properly work nvram save after reboot.

 

i returned this code from old script.

 

i checked it. brightness and other values are working.

 

you find solution to fix this issue from this hint.

 

i edited your latest script in dropbox.

 

thank you.

Cool. I just need to test it with a core storage volume too, which is needed for Fusion drives or FileVault.

 

Edit: It works as well. Thanks again.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

i found wrong code.

this is

 

it cause to not properly work nvram save after reboot.

 

i returned this code from old script.

 

i checked it. brightness and other values are working.

 

you find solution to fix this issue from this hint.

 

i edited your latest script in dropbox.

 

thank you.

Old script uses command "df -i" which will not find EFI partition and so can't be used for new purpose.

Link to comment
Share on other sites
smolderas
smolderas
Posted
Posted

Old script uses command "df -i" which will not find EFI partition and so can't be used for new purpose.

Although you are right, it is not necessary in this case. That line from Sherlocks is used only in fallback case, that means if the script can't find or can't save to EFI partition, it will fallback to root, which is fine with "df -i" even on core storage.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

i found wrong code.

this is

 

it cause to not properly work nvram save after reboot.

 

i returned this code from old script.

 

i checked it. brightness and other values are working.

 

you find solution to fix this issue from this hint.

 

i edited your latest script in dropbox.

 

thank you.

No, it is not safe to EFI

NVRAM saved to '/nvram.plist' [disk1s3]

It is root volume.

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

No, it is not safe to EFI

NVRAM saved to '/nvram.plist' [disk1s3]
It is root volume.
I just found this work or not work. I dont know how get work this.

 

I returned r3960 build until fix this issue.

 

나의 LG-F410S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

The script 3961 is not working for my comp #4 too.


For me the problem is "findFirstAppleBootDevice" which search for recovery. I have no it or have several HDD with several recovery.

Link to comment
Share on other sites
smolderas
smolderas
Posted
Posted

The script 3961 is not working for my comp #4 too.

For me the problem is "findFirstAppleBootDevice" which search for recovery. I have no it or have several HDD with several recovery.

I see. Could you please send me your "diskutil list". I'll look for a solution for everybody.

 

Edit: I need both outputs of these please:

diskutil list

and

diskutil info /
Link to comment
Share on other sites
Slice
Slice
Posted
Posted 


bash-3.2# diskutil list

/dev/disk0

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *250.1 GB   disk0

   1:       Microsoft Basic Data Win7Pro                 250.1 GB   disk0s1

/dev/disk1

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *250.1 GB   disk1

   1:                        EFI                         209.7 MB   disk1s1

   2:       Microsoft Basic Data Windows                 46.0 GB    disk1s2

   3:                  Apple_HFS MacHD                   113.6 GB   disk1s3

   4:         Microsoft Reserved                         133.2 MB   disk1s4

   5:       Microsoft Basic Data Data                    90.0 GB    disk1s5

/dev/disk2

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *1.0 GB     disk2

   1:                        EFI                         201.3 MB   disk2s1

   2:                  Apple_HFS Macintosh               821.6 MB   disk2s2

bash-3.2#

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

 

I see. Could you please send me your "diskutil list". I'll look for a solution for everybody.

 

Edit: I need both outputs of these please:

diskutil list

and

diskutil info /

 

report.

 

i updated 10.12.3 dp1 today. after updating osx, reboot system, clover automately enter windows drive(i installed windows 7).

i don't see problem in previous clover(r3960 or older). i set default boot volume "Macintosh SSD". but once fail. after booted windows 7, reboot system. i have to enter "Macintosh SSD". and 2nd boot, no problem.

 

maybe nvram has still problem. 

Link to comment
Share on other sites
smolderas
smolderas
Posted
Posted

report.

 

i updated 10.12.3 dp1 today. after updating osx, reboot system, clover automately enter windows drive(i installed windows 7).

i don't see problem in previous clover(r3960 or older). i set default boot volume "Macintosh SSD". but once fail. after booted windows 7, reboot system. i have to enter "Macintosh SSD". and 2nd boot, no problem.

 

maybe nvram has still problem. 

Check after reboot, if you have "efi-boot-device" in your NVRAM and post the result of the following after a reboot in macOS please:

bless --info --getBoot
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

 

Check after reboot, if you have "efi-boot-device" in your NVRAM and post the result of the following after a reboot in macOS please:

bless --info --getBoot

 

after installed clover from official r3691pkg

 

Last login: Thu Dec 15 17:30:31 on console

Supreme-MBP:~ supreme$ diskutil list

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *256.1 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:       Microsoft Basic Data Windows 7               110.0 GB   disk0s2

   3:       Microsoft Basic Data Win Data                60.1 GB    disk0s3

   4:                  Apple_HFS Macintosh SSD           69.1 GB    disk0s4

   5:                 Apple_Boot Recovery HD             650.0 MB   disk0s5

   6:                  Apple_HFS Mac Data                16.0 GB    disk0s6

 

Supreme-MBP:~ supreme$ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local

Password:

Supreme-MBP:~ supreme$ sudo nvram myvar="this is a new variable"

Supreme-MBP:~ supreme$ nvram -p|grep myvar

myvar this is a new variable

Supreme-MBP:~ supreme$ bdmesg|grep nvram.plist

0:387  0:000  Loading nvram.plist from Vol 'Macintosh SSD' - loaded, size=7326

Supreme-MBP:~ supreme$ bless --info --getBoot

Can't access "efi-boot-device" NVRAM variable

Supreme-MBP:~ supreme$ 

 

Link to comment
Share on other sites
smolderas
smolderas
Posted
Posted

after installed clover from official r3691pkg

Your issue with 10.12.3 has to do with clover can't correctly or won't set "efi-boot-device" in your NVRAM, and has nothing to do with the script. Please read the bug report.

bash-3.2# diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *250.1 GB   disk0
   1:       Microsoft Basic Data Win7Pro                 250.1 GB   disk0s1
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *250.1 GB   disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:       Microsoft Basic Data Windows                 46.0 GB    disk1s2
   3:                  Apple_HFS MacHD                   113.6 GB   disk1s3
   4:         Microsoft Reserved                         133.2 MB   disk1s4
   5:       Microsoft Basic Data Data                    90.0 GB    disk1s5
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 GB     disk2
   1:                        EFI                         201.3 MB   disk2s1
   2:                  Apple_HFS Macintosh               821.6 MB   disk2s2
bash-3.2#

Thanks. I think I have a working solution for everybody. I'll test it and post it soon.

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