smolderas

Is there a how to to migrate from sourceforge to GitHub? What do I need to do to re-initialise the gitlab locally on Mac? Edit: I see, there is a buildme script.

Hi Slice, can you please separate the boot chime from theme loading, so we can use boot chime while GUI->Fast is set to "true"?

Will it be possible to play the boot chime, while GUI->Fast is set to true?

Did you report this "bug"?

Yes, you need to boot into the other partition after first boot in order to be able to update... See previously comments.

Can't this update problem (at least on legacy) be solved with clover? Why would we need to boot manually in order to update.

I think it has to do with your mac model identifier.

I too have the same issue, I was trying to find the culprit. I'll take a look at it on the weekend.

I removed the file, and tried to build with ebuild.sh, same issue. Somewhere along there is an error. Edit: I found the culprit: Change the line 614 in the ebuild.sh to repoRev=$(svn info|awk '{ if ($1=="Revision:") {print $2}}') So here is the diff: 614c614 < repoRev=$(svn info | grep "Revision" | tr -cd [:digit:]) --- > repoRev=$(svn info|awk '{ if ($1=="Revision:") {print $2}}')

I removed the file, and tried to build with ebuild.sh, same issue. Somewhere along there is an error.

bdmesg started to report faulty version number: 3:616 0:000 Starting Clover revision: 01314556 on CLOVER EFI Do the ebuild.sh script update the Version.h file? Here is mine: #define FIRMWARE_BUILDDATE "2018-06-17 15:46:09" #define FIRMWARE_REVISION L"01314556" #define REVISION_STR "Clover revision: 01314556" #define BUILDINFOS_STR "Args: -n 9 -t XCODE8 --vbios-patch-cloverefi --only-sata0 --no-ext -D USE_LOW_EBDA -D NO_GRUB_DRIVERS -D NO_GRUB_DRIVERS_EMBEDDED -D EXIT_USBKB=1 --x64 | -D USE_LOW_EBDA -D NO_GRUB_DRIVERS -D NO_GRUB_DRIVERS_EMBEDDED -D EXIT_USBKB=1 -D ENABLE_VBIOS_PATCH_CLOVEREFI -D ONLY_SATA_0 -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.5 | XCODE: 9.4" So the script should be faulty...

I could test, if you publish the source.

I'm using FileVault2, so it's based on Core storage like fusion drive. It's set like this here: <key>DefaultVolume</key> <string>HD(2,GPT,159588F2-432D-4C37-A81C-5B788C3AA48A,0x64028,0xDF30B60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,2C597282D9D1154385E5FBD28A73FDF0)</string>

Yes, but I had that automatically before activating FileVault. I never had to boot into another partition manually. Does it have to do with nvram being not read? Edit: I don't know what you changed, but it didn't do anything for me...

Does that mean I could update normally without booting into another partition after restarting?