Jump to content
30960 posts in this topic

Recommended Posts

 

The script save_nvram... should automount ESP if not mounted.

In your script there is particular name

NVRAMMountPoint=/Volumes/EFI

But it is not the common case. It may be, for example, /Volumes/ESP.

 slice$ ls /Volumes/
Data		ESP		Macintosh	Win7Pro
EFI		MacHD		QEFI		Windows

I only added that, as that is the path used by "20.mount_ESP.local" to mount the partition on my system.

 

I can use every proposed script if:

1. I run the script manually BEFORE shutting down (Script mounts partition just fine in this case)

2. I mount the EFI partition manually BEFORE shutting down (Script does not mount the partition, but just saves the nvram.plist)

3. I use both "20.mount_ESP.local" and "80.save_nvram_plist.local" (Which is really the same as 2.) (All I did in my scripts is adding a new flag that gives more control, could just as well have used your script and "Clover.MountEFI=Yes").

 

Bottom line, the "80.save_nvram_plist.local" script won't mount the EFI partition when initiated on SIGTERM. (Which is probably the problem seen in #11981).

 

So I'm pretty sure that we need to do something before SIGTERM as joevt is saying in #11984. What I found is that we can't actually mount on SIGTERM, which is why it's bugging out.

But actually this affects nothing... I think this can be any text? Not confirmed.

Not sure if the release date matters. But IMO there's no need to store it - it can be retrieved from the ROM version: IM171.88Z.0105.B05.1511031741 = November 03 2015.

  • Like 2

But actually this affects nothing... I think this can be any text? Not confirmed.

Yeah. There is no affect date format actually.

 

I said that followed apple bios dump. Slice mentioned apple use xx/xx/xx in old bios. This is point. Clover follow apple's original format. Its not important Whether Affect or no affect system.

 

Date format is free if you want any format.

 

At least follow apple format is best

 

Thanks

 

 

 

나의 LG-F410S 의 Tapatalk에서 보냄

  • Like 1

I only added that, as that is the path used by "20.mount_ESP.local" to mount the partition on my system.

 

I can use every proposed script if:

1. I run the script manually BEFORE shutting down (Script mounts partition just fine in this case)

2. I mount the EFI partition manually BEFORE shutting down (Script does not mount the partition, but just saves the nvram.plist)

3. I use both "20.mount_ESP.local" and "80.save_nvram_plist.local" (Which is really the same as 2.) (All I did in my scripts is adding a new flag that gives more control, could just as well have used your script and "Clover.MountEFI=Yes").

 

Bottom line, the "80.save_nvram_plist.local" script won't mount the EFI partition when initiated on SIGTERM. (Which is probably the problem seen in #11981).

 

So I'm pretty sure that we need to do something before SIGTERM as joevt is saying in #11984. What I found is that we can't actually mount on SIGTERM, which is why it's bugging out.

Agree.

In the case EFI partition is not mounted the file will be saved into main partition?

Yeah. There is no affect date format actually.

 

I said that followed apple bios dump. Slice mentioned apple use xx/xx/xx in old bios. This is point. Clover follow apple's original format. Its not important Whether Affect or no affect system.

 

Date format is free if you want any format.

 

At least follow apple format is best

 

Thanks

 

 

 

나의 LG-F410S 의 Tapatalk에서 보냄

Not absolute. Some cases used xx/xx/xx and others used xx/xx/xxxx.

  • Like 1

Not absolute. Some cases used xx/xx/xx and others used xx/xx/xxxx.

Sorry my english. Like you said, i already checked bios dump and did it in latest commit.

 

Have a nice day

 

나의 LG-F410S 의 Tapatalk에서 보냄

Not absolute. Some cases used xx/xx/xx and others used xx/xx/xxxx.

Apple use UTC and en_US_posix almost always, and a date should be adjusted to display the local time zone. Icu library....(later i'll post a link)
  • Like 1

Alright. But how to check this in OS X/macOS?

What do you want? You can search darwin dump files in web sites. And find smbios.txt and you can see true that i said.

 

Anyway bios format of latest apple products is XX/XX/XXXX.

 

I want no more answer. I did answer enough.

 

 

 

나의 LG-F410S 의 Tapatalk에서 보냄

  • Like 2

@Slice

 

Some is miss when add commit.

 

"10/20/2015", // IM132

 

"10/20/2015", // IM161

 

"10/20/2015", // IM162

 

Change

"10/20/2016", // IM132

 

"10/20/2016", // IM161

 

"10/20/2016", // IM162

 

When you will add other commit, hope to reflect with this change.

 

Thanks

 

 

 

나의 LG-F410S 의 Tapatalk에서 보냄

The default logo is a white Apple on black background, and there is a progress bar below it. I'd like to have the gray Apple on white background, and with a progress bar. If I switch to "Apple" for CustomLogo in Clover Configurator->Boot, while I get the gray Apple on white background, but it doesn't come with a progress bar. clear.png

Is there anyway to get the progress bar?

Agree.

In the case EFI partition is not mounted the file will be saved into main partition?

Yes that is correct, but if nvram.plist is avaliable in EFI clover will still use that even after the fallback to save it into main partition, meaning that the nvram will not be up to date on the next boot.

 

In my case it will always use the nvram.plist from EFI partition even if the one in main partition is "newer".

What do you want? You can search darwin dump files in web sites. And find smbios.txt and you can see true that i said.

 

Anyway bios format of latest apple products is XX/XX/XXXX.

 

I want no more answer. I did answer enough.

 

 

 

나의 LG-F410S 의 Tapatalk에서 보냄

Whoops. I'd like to know how to check without the help of Internet... For example check this via a bash command?

i tested install clover pkg.

first i remove christmas and new year theme.

then, install clover pkg. clover automately install christmas and new year theme.

 

checked this folder. christmas theme is empty. new year theme has theme files.

 

here is clover log.

 

0:102  0:000  === [ GetListOfThemes ] ===================================

0:103  0:001  - [00]: bootcamp

0:104  0:001  - [01]: embedded

0:106  0:001  - [01]: random

0:107  0:001  - [01]: christmas - bad theme because theme.plist can't be load

0:107  0:000  - [01]: newyear

 

doesn't exist christmas theme files in latest clover pkg? 

 

add, change theme name bootcamp to christmas in GUI for test, christmas theme is not working.

maybe we will can't see christmas theme at 25 december of this year. :(

  • Like 1

I submited that question page 584 but got no answer then I found the solution.

 

It is not a Clover bug, but an Apple way of working which inserts a boot entry at startup.

 

You have to delete the hidden folder .IABootFiles at the root of your macOS drive.

 

 

I am trying to remove an entry from the Clover boot menu, or at least make it no longer the default choice. I have my config set to boot Macintosh HD by default, but instead it boots "Install from Macintosh HD" each time and promptly KPs.

 

It is a remnant of an old El Capitan Installer which does not link to any actual files and is not bootable. So far I have deleted the Install Data, cleared NVRAM, and entered the UEFI Shell so I could use bcfg, but it comes back every time (and Clover defaults to it instead of Macintosh HD). I am not trying to upgrade to El Cap, I already have El Cap installed.

Attached is my bcfg boot dump info, to which I then typed "bcfg boot rm 00" and followed with another dump. The entry showed as gone, but upon restart it was back again. Why does this keep coming back? How can I remove it permanently?

 

The is an X99 Deluxe with Clover 3961.

...

Thanks!

 

  • Like 1

I don't know if this helps you guys, but the device that Clover was started from is available from the Clover bootlog. The Clover bootlog is available from ioreg.

 

Note:

SPEEDY-NUC:~ rehabman$ bdmesg|grep SelfDevicePath
0:100  0:000  SelfDevicePath=PciRoot(0x0)\Pci(0x1D,0x0)\Pci(0x0,0x0)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,720CCE1B-927B-4261-9ED9-4126654A36CA,0x28,0x64000) @84486018

Is not it a device where clover found config.plist?

So I'm pretty sure that we need to do something before SIGTERM as joevt is saying in #11984. What I found is that we can't actually mount on SIGTERM, which is why it's bugging out.

rEFItBlesser is a solution for rEFIt that does a similar thing - mount the EFI partition at shutdown. It is a Startup Item as described at:

https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/StartupItems.html#//apple_ref/doc/uid/10000172i-SW9-CJBBHDII

 

I made some changes for rEFInd which seemed to work when I used it but I haven't used it recently. Startup Items are deprecated but I think they still work. Anyway, if the rEFItBlesser script works, then maybe it can help with this save_nvram_plist problem. You'll probably want to remove any part that uses the bless command, and just test the disk mounting feature (the if statement after the "mounted=0" line). Note that it uses "mount" instead of "df" to get a list of mount points. It also doesn't use diskutil. It uses /Users/Shared because other folders may not have permission?

 

The difference between a Startup Item and a Daemon is that a Startup Item defines dependencies. I think this is all handled by launchd, which you can look at the source code. Maybe the relevant parts could be converted to a Daemon.

rEFItBlesser.zip

  • Like 1

Is not it a device where clover found config.plist?

It indicates the partition from which Clover was started by BIOS.

And, yes... also the location of config.plist (Clover always loads the configuration from the same partition it was booted from).

Is not it a device where clover found config.plist?

I haven't checked. It doesn't matter. The take away here is that Clover can put any information we want there. If the information does not include the location of Clover, than Clover can be changed to add that. If device path is not usable by Mac OS X, Clover could add the partition GUID (either from GPT or from the filesystem).

 

To learn if device path is useable in Mac OS X, we should learn what kind of device paths the bless command creates, and how it does that.

 

We should make a routines that can be used in Mac OS X that can convert a device path between hex and text like GfxUtil but which can handle all cases as defined by EFI_DEVICE_PATH_TO_TEXT_PROTOCOL and EFI_DEVICE_PATH_FROM_TEXT_PROTOCOL. I think all the source code for this is in the UefiDevicePathLib folder of EDK2. GfxUtil only implements 2 device path node types, pci and acpi. UefiDevicePathLib has 44 others.

×
×
  • Create New...