Clover General discussion

[arsradu]

7 minutes ago, Alpha22 said:

I copied the EFI folder of usb to the hard disk

version of Clover 4558

the problem remains not booting from hard disk

Upload your EFI folder here for analysis. Remove serial numbers as suggested before.

Also, check your BIOS.

[Alpha22]

7 minutes ago, arsradu said:

Upload your EFI folder here for analysis. Remove serial numbers as suggested before.

Also, check your BIOS.

this is the EFI folder of the hard disk

I had the same problem if I remember correctly in El Capitan and they suggested me to format the hard disk EFI

but I do not remember how to do this

EFI.zip

Edited July 15, 2018 by Alpha22

[arsradu]

20 minutes ago, Alpha22 said:

this is the EFI folder of the hard disk

I had the same problem if I remember correctly in El Capitan and they suggested me to format the hard disk EFI

but I do not remember how to do this

EFI.zip

 

Disk Utility -> select the Hard Drive (not the partition) -> click Erase -> make sure the Scheme is set to GUID partition map and Format is MacOS Extended (Journaled).

 

 

Edited July 15, 2018 by arsradu

[Alpha22]

8 hours ago, arsradu said:

 

Disk Utility -> select the Hard Drive (not the partition) -> click Erase -> make sure the Scheme is set to GUID partition map and Format is MacOS Extended (Journaled).

 

 

I did not understand, but I have to redo a new installation setting the disk as reported

[arsradu]

 

Hi guys,

 

Is anyone else having Error 65 in MainMenu when compiling Clover on Mojave (using UDK2018)?

 

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
Updating 'en' strings file for CloverUpdater... done
Updating 'en' strings file for Clover Preference Panel... done
Updating strings file for Clover Preference Panel... done
 (170 entries)
Building CloverUpdater application...
** BUILD FAILED **


The following build commands failed:
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/zh_TW.lproj/MainMenu.xib
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/zh_CN.lproj/MainMenu.xib
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/uk.lproj/MainMenu.xib
(3 failures)
make: *** [CloverUpdater] Error 65
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

 

 

 

 

[Matgen84]

8 hours ago, arsradu said:

 

Hi guys,

 

Is anyone else having Error 65 in MainMenu when compiling Clover on Mojave (using UDK2018)?

 

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
Updating 'en' strings file for CloverUpdater... done
Updating 'en' strings file for Clover Preference Panel... done
Updating strings file for Clover Preference Panel... done
 (170 entries)
Building CloverUpdater application...
** BUILD FAILED **


The following build commands failed:
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/zh_TW.lproj/MainMenu.xib
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/zh_CN.lproj/MainMenu.xib
	CompileXIB /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverUpdater/src/uk.lproj/MainMenu.xib
(3 failures)
make: *** [CloverUpdater] Error 65
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

 

 

 

 

 

Same issue here with r4606 using UDK2018 on Mojave.

 

[SOLVED] Remove previous version, Install Xcode 10 Beta 4 and reinstall command lines tools (I'm not sure is necessary)

In cvad's script: I comment make pkg (line 502),  uncomment ./makepkg (line 501)

All work fines

 

Edited July 18, 2018 by Matgen84

[mrjayviper]

Removed

Edited July 19, 2018 by mrjayviper

[arsradu]

9 hours ago, Matgen84 said:

 

Same issue here with r4606 using UDK2018 on Mojave.

 

[SOLVED] Remove previous version, Install Xcode 10 Beta 4 and reinstall command lines tools (I'm not sure is necessary)

In cvad's script: I comment make pkg (line 502),  uncomment ./makepkg (line 501)

All work fines

 

 

Ok... Does it still make a package without that command....?

 

Also, I'm not sure this is really a fix...since I was able to compile it just fine with High Sierra using Xcode 9...and the same commands. Soo....something looks fishy to me.

[Matgen84]

39 minutes ago, arsradu said:

 

Ok... Does it still make a package without that command....?

 

Also, I'm not sure this is really a fix...since I was able to compile it just fine with High Sierra using Xcode 9...and the same commands. Soo....something looks fishy to me.

 

I thinks too something looks strange. All works fine with High Sierra without any change into v1.1.8 cavd's script. But  I can compile a package only with this modified line under Mojave Beta 4 (Xcode 10 Beta 4)

Edited July 18, 2018 by Matgen84

[arsradu]

58 minutes ago, Matgen84 said:

 

I thinks too something looks strange. All works fine with High Sierra without any change into v1.1.8 cavd's script. But  I can compile a package only with this modified line under Mojave Beta 4 (Xcode 10 Beta 4)

Right... I think it might do something to compile it.... Still, I was talking about compiling Clover with the default method. No custom scripts.

 

Still weird... Personally, I'm thinking this is probably some outdated methods/files which are no longer compatible with latest Xcode.

 

Update:

Quick question: in Mojave, did you build with Dark Mode ON or OFF? Amazingly enough, I can build with Dark Mode OFF (meaning Light Mode ON).

Also, looks like the problem is related to Dark Mode... Since Clover Prefpane seems to be white, even in Dark Mode.

 

Edited July 18, 2018 by arsradu

[vector sigma]

I made modifications and now works as expected (dark when dark and viceversa).

 

As soon I have more time Il made a commit, but I need to think a way for retro-compatibility.

[kylon]

@Sherlocks

 

hi sherlocks,

 

gma.c#1333

 

this is a duplicate of #13, line 1331

 

[Sherlocks]

1 hour ago, kylon said:

@Sherlocks

 

hi sherlocks,

 

gma.c#1333

 

this is a duplicate of #13, line 1331

 

 

now i'm making up framebuffer info from vit9696' script. soon i will commit clean info. thanks for report

[newuser]

Hello everyone! I have recently updated my xps 13 9343 from sierra 10.12.6 to high sierra 10.13.6. I know my all files are converted to apsf format and I need apsf.efi or apsfdriverloader.efi in EFI clover driversUEFI64 folder to load partition. I have dual boot Windows 10 as well. Once I place those files to that folder, clover won't boot as all. Without those files I can only see Windows partition. So now I am stuck half way. What could cause conflict? Is there any way to diagnose this issue?

[mrjayviper]

TLDR: (10.13.x) HFSplus can't detect any drives (including the USB stick OSX installer) on UEFI booting when I installed an older firmware on motherboard. VboxHFS+ works on UEFI boot. But I have experienced bootloop issues when I use VboxHFs + 4+TB HFS+ raid array but on legacy boot. 

 

No issues with HFSplus when using legacy booting.

 

I can use a legacy boot USB installer to install OSX but the HDD have the same issues when using UEFI boot.

---------------------

A month ago I updated the firmware (2018 version) on my Intel board and I got UEFI booting working. Clover+HFSplus.efi can detect my USB and the single HDD. I also have no bootloop issues when it comes to using a 4+TB HFS+ raid array. 

 

Because of other weird boot issues which I thought we're due to OSX, I moved back to Windows. But the weird boot issues area still present so I put back an older version (2017) of the firmware  and from what I can see, my boot issues on Windows have disappeared.

 

I decided to try OSX again last night. The problem is that when UEFi booting, HFSplus.efi can't detect any drives including the USB stick. I used VboxHFS just several hours ago, no issues with detecting drives.

 

But when I was testing OSX last month and was using VBoxHFS on legacy boot, I get bootloop issues when I have 4+TB HFS+ raid array.

 

I tried smaller raid array like 2x 80GB and I don't get any bootloop with that. My educated guess is that VboxHFS starts to get issues with raid arrays as the size increases.

 

Any ideas on how to:

1. Continue using HFSplus but using UEFI

2. OR use VbosHFS but no bootloop on raid arrays

 

Thanks

[arsradu]

3 hours ago, newuser said:

Hello everyone! I have recently updated my xps 13 9343 from sierra 10.12.6 to high sierra 10.13.6. I know my all files are converted to apsf format and I need apsf.efi or apsfdriverloader.efi in EFI clover driversUEFI64 folder to load partition. I have dual boot Windows 10 as well. Once I place those files to that folder, clover won't boot as all. Without those files I can only see Windows partition. So now I am stuck half way. What could cause conflict? Is there any way to diagnose this issue?

Can you remove your serials from SMBIOS and RTvariables and upload your entire EFI folder for analysis?

[Matgen84]

12 hours ago, arsradu said:

Right... I think it might do something to compile it.... Still, I was talking about compiling Clover with the default method. No custom scripts.

 

Still weird... Personally, I'm thinking this is probably some outdated methods/files which are no longer compatible with latest Xcode.

 

Update:

Quick question: in Mojave, did you build with Dark Mode ON or OFF? Amazingly enough, I can build with Dark Mode OFF (meaning Light Mode ON).

Also, looks like the problem is related to Dark Mode... Since Clover Prefpane seems to be white, even in Dark Mode.

 

 

 

I don't install CloverPrefpane in System/settings.

 

Yes, I compile in Dark mode in Mojave Beta 4. I test cavd release v1.1.9

 

1. compile with existing src folder (create with 1.1.8 modified): all works fine 

2. compile clean src folder: error 65 make pkg

[arsradu]

9 minutes ago, Matgen84 said:

 

I don't install CloverPrefpane in System/settings.

 

Yes, I compile in Dark mode in Mojave Beta 4. I test cavd release v1.1.9

 

1. compile with existing src folder (create with 1.1.8 modified): all works fine 

2. compile clean src folder: error 65 make pkg

 

OK, thank you.

 

Waiting for vector sigma to push the changes up.

[mrjayviper]

Is this the right place to talk about compiling and other developer talk? Seems it's more appropriate to talk about that in the clover development section. And leave the "normal" clover users to this thread?

Edited July 19, 2018 by mrjayviper

[arsradu]

29 minutes ago, mrjayviper said:

Is this the right place to talk about compiling and other developer talk? Seems it's more appropriate to talk about that in the clover development section. And leave the "normal" clover users to this thread?

Well, you would be right. Except regular users cannot post in the development thread.

[mrjayviper]

edited.....

Edited July 19, 2018 by mrjayviper

[mrjayviper]

How can I disable scanning of entries during clover boot?

 

I've tried the settings on the screenshot and Auto=Yes  (which disables all the checkboxes inside the scan section) but it's still happening.

 

Thanks

 

[arsradu]

18 minutes ago, mrjayviper said:

How can I disable scanning of entries during clover boot?

 

I've tried the settings on the screenshot and Auto=Yes  (which disables all the checkboxes inside the scan section) but it's still happening.

 

Thanks

 

 

Well, unchecking Entries should do the trick. I'm thinking maybe the drive you're booting from is not actually the one using this config? Cause I've got that disabled, and there is no "Scanning entries..." in Clover boot. Or...maybe you have multiple config.plist files?

 

Update:

 

Try Boot -> NoEarlyProgress.

Edited July 19, 2018 by arsradu

[mrjayviper]

another question please.

 

If I don't need something to show up (or scanned), I can delete the EFI driver. correct?

 

example: I don't want the Windows OS/data partitions to be shown/scanned so I can delete and NTFS driver. Or in Linux case, I can delete any of the extX drivers.

 

Thanks

Edited July 19, 2018 by mrjayviper

[Slice]

51 minutes ago, mrjayviper said:

another question please.

 

If I don't need something to show up (or scanned), I can delete the EFI driver. correct?

 

example: I don't want the Windows OS/data partitions to be shown/scanned so I can delete and NTFS driver. Or in Linux case, I can delete any of the extX drivers.

 

Thanks

Quite correct.