Bootloader Clover problems report & features request

[jerryy2]

I hope this is the right place to ask for help, if not please forgive me and direct me to the correct place...

 

I successfully updated Clover from version 4558 to the new 4586 but immediately ran into a problem in that after the initial clover screen appears and the boot process is started, the screen goes black, the Apple screen progress bar does not appear and the system seems to hang. Pressing the restart button causes the system to go into a panic type rebooting over and over again cycle.

 

The problem, at a surface glance, seems to be an issue with the 4k monitor's chosen default resolution. Here is the tail of the debug log entry:

 

29:011  0:036  SetScreenResolution: 3840x2160 - already set
29:038  0:027  Custom boot is disabled
29:053  0:014  Closing log
39:347  10:293  Custom boot screen is not locked
39:360  0:013  Failed to unlock custom boot screen: Not Ready!
 

I have included the full debug log entry which has all of the system information included in it. I tried the installation on this system on two different os disks, one for 10.13 and one for 10.14 beta with the same result. Going back to version 4558 did work is all that seems to work at the moment.

 

Thank you for your help.

debug v4586.txt.zip

[apianti]

25 minutes ago, jerryy2 said:

I hope this is the right place to ask for help, if not please forgive me and direct me to the correct place...

 

I successfully updated Clover from version 4558 to the new 4586 but immediately ran into a problem in that after the initial clover screen appears and the boot process is started, the screen goes black, the Apple screen progress bar does not appear and the system seems to hang. Pressing the restart button causes the system to go into a panic type rebooting over and over again cycle.

 

The problem, at a surface glance, seems to be an issue with the 4k monitor's chosen default resolution. Here is the tail of the debug log entry:

 

29:011  0:036  SetScreenResolution: 3840x2160 - already set
29:038  0:027  Custom boot is disabled
29:053  0:014  Closing log
39:347  10:293  Custom boot screen is not locked
39:360  0:013  Failed to unlock custom boot screen: Not Ready!
 

I have included the full debug log entry which has all of the system information included in it. I tried the installation on this system on two different os disks, one for 10.13 and one for 10.14 beta with the same result. Going back to version 4558 did work is all that seems to work at the moment.

 

Thank you for your help.

debug v4586.txt.zip

 

Looks like Custom boot screen is failing for some reason. Make sure you have all the drivers you need or just stay on whatever version works for now. 

[jerryy2]

54 minutes ago, apianti said:

 

Looks like Custom boot screen is failing for some reason. Make sure you have all the drivers you need or just stay on whatever version works for now. 

 

Thank you for your reply.

 

I used the same drivers as for version 4558, at least the same named drivers anyway, I am guessing the v4586 Clover installer/updater installed newer versions of them. Right now, I have dropped back to version 4558 to be able to run the system.

[apianti]

On 6/17/2018 at 3:24 PM, chris1111 said:

apianti WIKI Connections works here 

 

 

On 6/17/2018 at 4:05 PM, Maniac10 said:

After that screen it fails saying:

 

Authentication failed

Insufficient data from authentication provider, email not provided or empty

 

This is the exact behavior I am getting, the initial authorization works but not after.

On 6/18/2018 at 2:01 AM, JrCs said:

For the clover wiki authentification, you need to provide a NAME and an EMAIL in your github profile.

 

I have both of these as well. But I figured out that if I enabled my email to be public, then disabled it to be private again, I can now log in. So it seems it may actually be a problem with github, since even though it was telling me it failed I was signed into github. It appears to be working for me now though. Thanks!

[apianti]

1 hour ago, jerryy2 said:

 

Thank you for your reply.

 

I used the same drivers as for version 4558, at least the same named drivers anyway, I am guessing the v4586 Clover installer/updater installed newer versions of them. Right now, I have dropped back to version 4558 to be able to run the system.

 

Sorry, I didn't see you had your log before but bro, I see your issue, no AptioFix driver:

0:338  0:016  === [ LoadDrivers ] =======================================
0:909  0:571  Loading AppleImageCodec-64.efi  status=Success
0:951  0:042  Loading AppleUITheme-64.efi  status=Success
0:993  0:042  Loading DataHubDxe-64.efi  status=Success
1:039  0:045  Loading AppleKeyAggregator-64.efi  status=Success
1:081  0:041  Loading VBoxHfs-64.efi  status=Success
1:123  0:042   - driver needs connecting
1:136  0:013  Loading FSInject-64.efi  status=Success
1:179  0:042  Loading FirmwareVolume-64.efi  status=Success
1:232  0:053  Loading SMCHelper-64.efi  status=Success
1:274  0:042  Loading apfs.efi  status=Success
1:318  0:043   - driver needs connecting
1:331  0:013  2 drivers needs connecting ...

You also have your memory in the wrong slots, you should switch them to the other slots:

23:026  0:361  SMBIOS Type 17 Index = 0 => 0 0:
23:048  0:022  BANK 0 DIMM0 EMPTY
23:062  0:013  SMBIOS Type 17 Index = 1 => 2 2:
23:076  0:013  BANK 1 DIMM0 EMPTY
23:089  0:013  SMBIOS Type 17 Index = 2 => 1 1:
23:103  0:013  BANK 0 DIMM1 2666MHz 16384MB
23:117  0:013  SMBIOS Type 17 Index = 3 => 3 3:
23:131  0:013  BANK 1 DIMM1 2666MHz 16384MB

 

[griven]

I'am unsure if this has reported or discussed before. If so please ignore my post...

It seems as if macOS Mojave has some "special requirements" about BootVolume/InstallVolume assignments. Here is what I did:

 

I have 2 drives in my rig, both apfs formatted, one of them holds HighSierra as my daily driver and the Clover bootloader on it's EFI partition the other one is a spare drive for testing purpose. I cloned an existing clean Mojave install onto the spare drive for testing purpose which booted quite nice with clover installed on my primary drive. Today Apple rushed out Beta3 of Mojave and so I decided to give it a try. The 1st stage of the update loaded and installed fine and the 2nd stage also started fine but quits with an error "macOS could not be installed.... Installer Sources could not be found..." I took a look at the installers log and it states that it could not find installer files on my primary drive, the one Clover starts from (called Sierra as the one which should be updated is called Mojave)...

 

It also does not matter wether you want to update or do a clean Install onto an empty disk you'll always will end up in an error message stating "Installer Resources could not be found" if the 2nd Stage is not booted from the drive it should be installed on. Is there any way to pass the booted device UUID to macOS instead of the one the bootloader started from?

Edited July 4, 2018 by griven

[jerryy2]

20 hours ago, apianti said:

 

Sorry, I didn't see you had your log before but bro, I see your issue, no AptioFix driver:

0:338  0:016  === [ LoadDrivers ] =======================================
0:909  0:571  Loading AppleImageCodec-64.efi  status=Success
0:951  0:042  Loading AppleUITheme-64.efi  status=Success
0:993  0:042  Loading DataHubDxe-64.efi  status=Success
1:039  0:045  Loading AppleKeyAggregator-64.efi  status=Success
1:081  0:041  Loading VBoxHfs-64.efi  status=Success
1:123  0:042   - driver needs connecting
1:136  0:013  Loading FSInject-64.efi  status=Success
1:179  0:042  Loading FirmwareVolume-64.efi  status=Success
1:232  0:053  Loading SMCHelper-64.efi  status=Success
1:274  0:042  Loading apfs.efi  status=Success
1:318  0:043   - driver needs connecting
1:331  0:013  2 drivers needs connecting ...

You also have your memory in the wrong slots, you should switch them to the other slots:

23:026  0:361  SMBIOS Type 17 Index = 0 => 0 0:
23:048  0:022  BANK 0 DIMM0 EMPTY
23:062  0:013  SMBIOS Type 17 Index = 1 => 2 2:
23:076  0:013  BANK 1 DIMM0 EMPTY
23:089  0:013  SMBIOS Type 17 Index = 2 => 1 1:
23:103  0:013  BANK 0 DIMM1 2666MHz 16384MB
23:117  0:013  SMBIOS Type 17 Index = 3 => 3 3:
23:131  0:013  BANK 1 DIMM1 2666MHz 16384MB

 

 

Hello again,

 

Your answer was on the mark. It seems in v4558 the driver is called AptioMemoryFix.efi but in v4586 it has been renamed to AptioMemoryFix-64.efi and even though I use the custom install method to double check what is supposed to be installed, I managed to miss that the installer's auto-select method of upgrading already installed drivers did not select it.

 

Thank you very much for your help!

 

p.s. About the dimm slot choices, that comes from the motherboard user manual for a two dimm setup, using either pair is supposed to be okay, so the physical layout of the slots next to the cpu which then has the cpu cooler almost covering one of the dimm slots came into consideration. Right now, when prices come back into my affordability range so I can add the next pair, I will not have to take off the cpu cooler to do it.

[Oliver@Cheme]

Hello!
It seems there is a bug with RC Scripts for saving nvram.plist in latest Clover revisions (e.g. 4586) when installed in legacy mode in Snow Leopard (10.6.8). The nvram is not saved and a forced shutdown is required (Normal shutdown does not occur when scripts are installed, the system stucks at final black screen before complete shutdown). After login, high CPU usage is verified when RC scripts are installed. Checking the System Monitor, this is caused by a process named SED. All these issues don't occur with newer releases of macOS. Is OS X 10.6 incompatible with latest versions of these scripts or is this really a bug? Thanks.

Edited July 9, 2018 by Oliver@Cheme

[Slice]

10.6 has a mistake in nvram support. As a workaround you may delete AppleEFIRuntime.kext.

[drphilth]

Hello,

 

 

I have a quick question. What was the last clover release to use fdisk440 to install the bootloader files for non uefi boot?

 

I have had some trouble getting clover to install and boot on an old ga-x58a-ud3r, and was going mad trying to figure it out. I tried an older version (r4128) of clover and it worked. I noticed in the install logs that r4128 used fdisk440 but r4586 tried to use dd. 

 

For now, it works is I install r4128 first (just the bootloader) and then immediately install r4586 (full install) after it.

 

Also, is this a bug or is this intended behaviour after removing the "legacy boot" parts of clover?

 

 

Thanks!

[mrjayviper]

I created a UEFI USB installer and my UEFI setup cannot boot using it. I tried a UEFI Ubuntu USB installer and that works fine.

 

I inspected both sticks using the motherboard EFI shell and I can see that the EFI folder created by clover doesn't have the attribute of D (D for directory) hence the motherboard firmware cannot see the bootloader.

 

The fix I had to do is to run these commands inside motherboard EFI shell:

1. fsX: (change to correct location of the USB stick)

2. attrib * (to display all the attributes of files/folders. The EFI folder has no D attribute at this point. It does does the archive attribute set. The other OSX system folders like .FSxxx have one)

3. attrib -a EFI (strips the EFI of its attributes. for some reason this also creates a new file called EFI)

4. del EFI (deletes the EFI file)

5. attrib * (to display the attributes again and this time the EFI folder has a D attribute)

 

Can this be fix by Clover?

 

Thanks!

[Slice]

Clover don't create EFI folder. It is the job for other software.

[Badruzeus]

Hi @Sherlocks, among other devs && coders,

I propose this new "Antergos" entry (Linux, based on Arch). Thanks.

[Sherlocks]

Hi [mention=980913]Sherlocks[/mention], among other devs && coders,
I propose this new "Antergos" entry (Linux, based on Arch). Thanks.

i will check. thanks

나의 LG-F800S 의 Tapatalk에서 보냄

[WeBeRiO]

Wow! the new design is very beautifil. Thank  plasplasplas

Is visually attractive down a bit the logo and center like sample.

 

[chris1111]

5 hours ago, WeBeRiO said:

Wow! the new design is very beautifil. Thank  plasplasplas

Is visually attractive down a bit the logo and center like sample.

 

Original logo correct center and adjust

Let me know if this one is OK 

background.tiff.zip

Edited August 2, 2018 by chris1111

[oSxFr33k]

I would like to report a bug in v4630 Legacy Bios Install, boot to cursor of death. 

 

Steps to reproduce:

 

1)  I used a Samsung SSD EVO 860 512GB to format Mac OS Extended (Journaled) then freshly install MacOS 10.13.6.

2)  Used flash drive with Clover to boot fresh MacOS install

3)  Installed Clover v4630 onto SSD fresh no prior clover versions.

 

Steps to Solve:

 

1)  install a prior known working version onto SSD, I went all the way back to v4097.

2)  Upgraded to v4630

3)  No issues encountered.

Edited August 5, 2018 by oSxFr33k
Clerical error on version number

[Matgen84]

1 hour ago, oSxFr33k said:

I would like to report a bug in v4360 Legacy Bios Install, boot to cursor of death. 

 

Steps to reproduce:

 

1)  I used a Samsung SSD EVO 860 512GB to format Mac OS Extended (Journaled) then freshly install MacOS 10.13.6.

2)  Used flash drive with Clover to boot fresh MacOS install

3)  Installed Clover v4360 onto SSD fresh no prior clover versions.

 

Steps to Solve:

 

1)  install a prior known working version onto SSD, I went all the way back to v4097.

2)  Upgraded to v4360

3)  No issues encountered.

 

Hi

 

Latest release is r4630. You can use it instead of r4360.

[fusion71au]

 

I can confirm this problem.  When installing the latest Clover versions in legacy mode on a new drive, boot0af is not being correctly installed in the MBR (but boot1f32 installs OK in the PBR).  Relevant part of Clover r4636 install log shown in spoiler...

 

Spoiler

 

Installer version: v2.4k r4636 EFI bootloader
======================================================
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *53.7 GB    disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS macOS                   53.3 GB    disk0s2

/dev/disk1 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *512.5 MB   disk1
   1:                 DOS_FAT_32 CLOVER                  510.7 MB   disk1s1

======================================================
Backing up EFI files

Backing up stage2 file /Volumes/CLOVER/EFIROOTDIR/boot  to /Volumes/CLOVER/EFI-Backups/r4636/2018-08-05-22h17/boot
Backing up /Volumes/CLOVER/EFIROOTDIR/EFI folder to /Volumes/CLOVER/EFI-Backups/r4636/2018-08-05-22h17/EFI
Current Active Partition: 1

Stage 0 - Writting boot0af to /dev/disk1
dd: /Volumes/CLOVER/usr/standalone/i386/boot0af -> /dev/disk1

Stage 1 - Writting boot1f32 to /dev/rdisk1s1
dd if=/dev/rdisk1s1 count=1 bs=512 of=/tmp/origbs
boot volume format is FAT32
cp /tmp/boot1f32 /tmp/newbs
dd if=/tmp/origbs of=/tmp/newbs skip=3 seek=3 bs=1 count=87 conv=notrunc
dd if=/tmp/newbs of=/dev/rdisk1s1

Setup Active Partition to be: 1
New Active Partition: 1

Stage 2 - Written boot6 (x64) to /Volumes/CLOVER/boot

======================================================
=========== Clover EFI Installation Finish ===========
======================================================

 

 

 

 

Seems like regression caused by r4541 (uses dd to install boot sectors instead of fdisk440).  Using Bootice 64 bit in windows to install boot0af to MBR (or installing boot sectors with Clover version older than r4541 first) restores booting ability.

 

Edit Can manually install boot0af to target disk MBR with dd from terminal ...

1.  Download i386 folder (attached to this post) with boot0af inside to your ~/Downloads folder

2.  Determine disk number of target disk with diskutil list command - in my case, USB = disk1

3.  Unmount target disk

sudo diskutil unmountDisk rdisk1

4.  Write boot0af to MBR with dd

sudo dd if=/dev/rdisk1 bs=512 count=1 of=~/Downloads/i386/origMBR
cp ~/Downloads/i386/origMBR ~/Downloads/i386/newMBR
sudo dd if=~/Downloads/i386/boot0af of=~/Downloads/i386/newMBR bs=440 count=1 conv=notrunc
sudo dd if=~/Downloads/i386/newMBR of=/dev/rdisk1 count=1 bs=512
sudo diskutil mountDisk rdisk1

 

i386.zip

Edited August 7, 2018 by fusion71au
Procedure to manually install boot0af with dd from terminal

[oSxFr33k]

6 hours ago, Matgen84 said:

 

Hi

 

Latest release is r4630. You can use it instead of r4360.

 

Sorry meant 4630. 

[cmyk]

I had rev 4458 on boot SSD. Updated it to 4630 and thereafter the Hackintosh rebooted after clover screeen.

Had to boot from USB stick and restore the EFI partition.

 

[Joni_78]

I tried Windows 10 on my hackintosh #1 on the sig. Same BIOS settings that I use with macOS. I noticed that on recent Windows 10 builds when I turn on or reboot to do a full reboot, BIOS logo screen is completely disabled. It will instantly go to the Windows logo.

 

On Clover/macOS I'll see the BIOS logo screen and after that the Apple logo. Would it be possible to bypass BIOS screen completely with Clover, so that it would go directly to Apple logo on boot?

[Slice]

Clover works after BIOS.

[Trung_Nguyen]

[PROBLEM REPORT]

Hello, I'm using FileVault 2 of macOS Mojave beta 6.

Clover version 4644

The EFI login screen took too long(as long as booting the kernel).

When I use the -v, there are spamming of message "smcProtocol->SmcReadValue failed for key "blah"" after the LoginWindow loaded

Not sure if it is related to SMCHelper or not?

Thanks

Edited August 13, 2018 by Trung_Nguyen
add clover version

[Slice]

Yes, it is related to SMCHelper. It reported that the key "blah" is absent is nvram.

It should be looking in boot.log as follow

1:300  0:060  Loading nvram.plist from Vol 'MacHD' - loaded, size=3072
1:327  0:026  === [ PutNvramPlistToRtVars ] =============================
1:327  0:000   Adding Key: ActualDensity: Size = 2, Data: E1 00 
1:327  0:000   Adding Key: BootCampHD: Size = 32, Data: 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 02 1F 03 12 0A 00 00 00 00 00 00 00 7F FF 04 00 
1:327  0:000   Adding Key: DensityThreshold: Size = 2, Data: 96 00 
1:327  0:000   Adding Key: EFILoginHiDPI: Size = 4, Data: 01 00 00 00 
1:327  0:000   Skipping EmuVariableUefiPresent
1:327  0:000   Adding Key: IOHibernateRTCVariables: Size = 44, Data: 41 41 50 4C 01 00 00 00 99 06 1D 18 CE 2D 50 43 FA C4 5C 8D AD DA D6 32 7D 5A F6 C1 7F 0E F1 DE 5B 23 C8 31 49 E2 52 E2 25 48 BD 68 
1:327  0:000   Adding Key: LocationServicesEnabled: Size = 1, Data: 01 
1:327  0:000   Adding Key: backlight-level: Size = 2, Data: 01 01 
1:327  0:000   Adding Key: boot-args: String: Size = 10, Val = 'nvda_drv=1'
1:327  0:000   Adding Key: bootercfg: Size = 2, Data: 28 00 
1:327  0:000   Adding Key: csr-active-config: Size = 4, Data: E7 03 00 00 
1:327  0:000   Adding Key: efi-boot-device: Size = 216, Data: 3C 61 72 72 61 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 49 4F 4D 61 74 63 68 3C 2F 6B 65 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 49 4F 50 72 6F 76 69 64 65 72 43 6C 61 73 73 3C 2F 6B 65 79 3E 3C 73 74 72 69 6E 67 3E 49 4F 4D 65 64 69 61 3C 2F 73 74 72 69 6E 67 3E 3C 6B 65 79 3E 49 4F 50 72 6F 70 65 72 74 79 4D 61 74 63 68 3C 2F 6B 65 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 55 55 49 44 3C 2F 6B 65 79 3E 3C 73 74 72 69 6E 67 3E 39 42 38 46 33 42 39 41 2D 46 31 33 45 2D 34 36 44 41 2D 41 38 45 38 2D 43 42 42 34 35 39 30 34 45 31 35 34 3C 2F 73 74 72 69 6E 67 3E 3C 2F 64 69 63 74 3E 3C 2F 64 69 63 74 3E 3C 2F 64 69 63 74 3E 3C 2F 61 72 72 61 79 3E 
1:327  0:000   Adding Key: efi-boot-device-data: Size = 74, Data: 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 02 1F 03 12 0A 00 00 00 FF FF 00 00 04 01 2A 00 05 00 00 00 90 19 75 0E 00 00 00 00 D8 71 BA 16 00 00 00 00 9A 3B 8F 9B 3E F1 DA 46 A8 E8 CB B4 59 04 E1 54 02 02 7F FF 04 00 
1:327  0:000   Adding Key: fakesmc-key-#KEY-ui32: Size = 4, Data: 00 00 00 11 
1:327  0:000   Adding Key: fakesmc-key-$Adr-ui32: Size = 4, Data: 00 00 03 00 
1:327  0:000   Adding Key: fakesmc-key-$Num-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-BATP-flag: Size = 1, Data: 00 
1:327  0:000   Adding Key: fakesmc-key-BBIN-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-BEMB-flag: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-BNum-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-CLKH-{clh: Size = 8, Data: 00 00 70 80 00 01 19 40 
1:327  0:000   Adding Key: fakesmc-key-CLKT-ui32: Size = 4, Data: 00 01 3C B8 
1:327  0:000   Adding Key: fakesmc-key-EPCI-ui32: Size = 4, Data: 06 40 07 00 
1:327  0:000   Adding Key: fakesmc-key-HE0N-ui8: Size = 1, Data: 0E 
1:327  0:000   Adding Key: fakesmc-key-MSAc-ui16: Size = 2, Data: 00 00 
1:327  0:000   Adding Key: fakesmc-key-MSDW-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-MSFW-ui8: Size = 2, Data: 01 00 
1:327  0:000   Adding Key: fakesmc-key-MSPS-ui16: Size = 2, Data: 00 03 
1:327  0:000   Adding Key: fakesmc-key-MSTc-ui8: Size = 1, Data: 00 
1:327  0:000   Adding Key: fakesmc-key-MSWr-ui8: Size = 1, Data: 00 
1:327  0:000   Adding Key: fakesmc-key-NATJ-ui8: Size = 1, Data: 02 
1:327  0:000   Adding Key: fakesmc-key-NATi-ui16: Size = 2, Data: 00 1E 
1:327  0:000   Adding Key: fakesmc-key-NTOK-ui8: Size = 1, Data: 01 
1:327  0:000   Adding Key: fakesmc-key-RBr -ch8*: Size = 8, Data: 64 32 00 6A 31 33 00 00 
1:327  0:000   Adding Key: fakesmc-key-REV -ch8*: Size = 6, Data: 02 03 0F 00 00 36 
1:327  0:000   Adding Key: fakesmc-key-RMde-char: Size = 1, Data: 41 
1:327  0:000   Adding Key: fakesmc-key-RPlt-ch8*: Size = 8, Data: 64 32 00 00 00 00 00 00