Jump to content
30960 posts in this topic

Recommended Posts

2 hours ago, netgear said:

I replicated on another HDD, reset NVram, a custom Entries that points to shimx64.efi.
Versions 5114 and earlier launch.
The 5115 does not start, grubx64.efi or EFISTUB starts, does not stop, the disk runs continuously without stopping, it cannot load GRUB or tries to do it, ctrl, alt, cancel restarts.

Well, according to my tests on Qemu, I observe this:

1) shimx64.efi works if it loads directly

2) shimx64.efi does NOT work and "hangs" in both cases:

- when started from Shell (shell starts directly from UEFI, without any Clover)

- when started from Clover. This is true also with older clover.

I am not sure why it hangs when it is not started directly.


You can test also, I am quite sure it will also not start from Shell for you as well.

What I don't understand is how it worked for you from older Clover, as it doesn't load even from shell. Maybe you had some nvram variables that are gone after the nvram reset, that made it work in the past.

Anyway, if you can find a way to make it work from shell, I may be able to help to make it work from clover.

 

EDIT: do you specify any load options for shimx64.efi in your custom entry?

Edited by Pene
  • Like 2
2 hours ago, vector sigma said:

you're welcome

 

already told you

 

set only ProductName and BoardSerialNumber....  and don't do any other thing (Clover knows what to do).

 

no

happy for you :)

Thanks again.

My BIOS question was about BIOS PARAMETERS LIKE:

EIST better enabled or disabled?

CPU C States (enabled in my case)

CPU C3 REPORT (enabled in my case)

CPU C6 REPORT (enabled in my case)

PACKAGE C STATE LIMIT (C6 (no retention) State-in my case)

 

:) Your solution works better in Catlina than Mojave with patches in my case.

Would you mind to list the Mojave patches just to double check they are right in my case?


It is very kind of you. Best wishes 

 

1 hour ago, jlcdgd said:

Would you mind to list the Mojave patches just to double check they are right in my case?

EIST enabled/disabled depend from your choice. I like it enabled, but if I was looking for performance probably I'll left it disabled... but as I said instead I like stability, low noise and so I want my cpu cooler as possible. Not sure what patches you need, but between mojave and catalina the patch is almost the same.... I've added only a patch to surpass a little if statement Apple added on top of the xcpm_boostrap() function in 10.15.4+ and bring back everythings as before, i.e no need to set a fake cpu id to deceive macOS but let cpus we know are already capable of work with xcpm.. doing it.

Edited by vector sigma
s

Entries GRUB + EFISTUB, for 20.04 Path e initrd.img \boot\

-

Spoiler

<dict>
                    <key>Disabled</key>
                    <false/>
                    <key>FullTitle</key>
                    <string>Ubuntu GRUB</string>
                    <key>Hidden</key>
                    <true/>
                    <key>Ignore</key>
                    <false/>
                    <key>Image</key>
                    <string>\EFI\CLOVER\themes\Buttons\icons\os_ubuntu.icns</string>
                    <key>Path</key>
                    <string>\EFI\ubuntu\shimx64.efi</string>
                    <key>Type</key>
                    <string>Linux</string>
                    <key>Volume</key>
                    <string>05B7CBBE-F484-4FED-90D2-93CDCA5552F4</string>
                    <key>VolumeType</key>
                    <string>Internal</string>
                </dict>
                <dict>
                    <key>Arguments</key>
                    <string>initrd=initrd.img quiet splash root=PARTUUID=E804AB32-8330-4A45-85AD-F7A8CD2D88DE ro</string>
                    <key>Disabled</key>
                    <false/>
                    <key>FullTitle</key>
                    <string>Ubuntu</string>
                    <key>Ignore</key>
                    <false/>
                    <key>Image</key>
                    <string>\EFI\CLOVER\themes\Buttons\icons\os_ubuntu.icns</string>
                    <key>Path</key>
                    <string>\vmlinuz</string>
                    <key>Type</key>
                    <string>Linux</string>
                    <key>Volume</key>
                    <string>E804AB32-8330-4A45-85AD-F7A8CD2D88DE</string>
                    <key>VolumeType</key>
                    <string>Internal</string>
                </dict>

 

  • Like 1

Issues with 5115

 

I'd first ask if anyone has experienced issues with latest Xcode 14

The issue i'm actually having is : impossible boot clover after building 

 

yesterday i updated Xcode to last revision.

then updating also clover to 5115 build went fine no errors at all.

so i installed and tried to boot. BUT it didn't.

After selecting the volume it stay frozen at apple logo.

 

so to get an idea about the possible cause i went to clover releases and got the zipped file from there

replaced the boot files and it booted...

 

(only curious thing noticed, the size of BOOTX64 was a little more then 1mb, compared to old one around 920kb)

 

is this related to xcode or....? anyone else but me had this?

  • Confused 1

Hi LabyOne, I'm booting with Clover built some minutes ago using Xcode 11.4.1 (11E503a) in Catalina 10.15.5 Beta 3 (19F72f), of course using GCC53 as toolchain. Size is 928.064 bytes. 

CLOVERX64.efi.zip

Edited by vector sigma
  • Like 1
  • Thanks 1
1 hour ago, vector sigma said:

Hi LabyOne, I'm booting with Clover built some minutes ago using Xcode 11.4.1 (11E503a) in Catalina 10.15.5 Beta 3 (19F72f), of course using GCC53 as toolchain. Size is 928.064 bytes. 

CLOVERX64.efi.zip

could it be related to XCODE8 build?

 

EDIT:

yep!!

it seems its a Xcode8 issue, rebuilt with GCC53 and size is smaller and boot...

Edited by LAbyOne
5 minutes ago, LAbyOne said:

could it be related to XCODE8 build?

Link Time Optimization is not enabled with clang, so yes gcc produces smaller binaries and so is normal. Attached clover built with XCODE8 toolchain (sorry can't reboot as I wont to lose the undo stack). Size is 996.480 bytes.

CLOVERX64.efi.zip

11 hours ago, netgear said:

Entries GRUB + EFISTUB, for 20.04 Path e initrd.img \boot\

-

  Reveal hidden contents

<dict>
                    <key>Disabled</key>
                    <false/>
                    <key>FullTitle</key>
                    <string>Ubuntu GRUB</string>
                    <key>Hidden</key>
                    <true/>
                    <key>Ignore</key>
                    <false/>
                    <key>Image</key>
                    <string>\EFI\CLOVER\themes\Buttons\icons\os_ubuntu.icns</string>
                    <key>Path</key>
                    <string>\EFI\ubuntu\shimx64.efi</string>
                    <key>Type</key>
                    <string>Linux</string>
                    <key>Volume</key>
                    <string>05B7CBBE-F484-4FED-90D2-93CDCA5552F4</string>
                    <key>VolumeType</key>
                    <string>Internal</string>
                </dict>
                <dict>
                    <key>Arguments</key>
                    <string>initrd=initrd.img quiet splash root=PARTUUID=E804AB32-8330-4A45-85AD-F7A8CD2D88DE ro</string>
                    <key>Disabled</key>
                    <false/>
                    <key>FullTitle</key>
                    <string>Ubuntu</string>
                    <key>Ignore</key>
                    <false/>
                    <key>Image</key>
                    <string>\EFI\CLOVER\themes\Buttons\icons\os_ubuntu.icns</string>
                    <key>Path</key>
                    <string>\vmlinuz</string>
                    <key>Type</key>
                    <string>Linux</string>
                    <key>Volume</key>
                    <string>E804AB32-8330-4A45-85AD-F7A8CD2D88DE</string>
                    <key>VolumeType</key>
                    <string>Internal</string>
                </dict>

 

OK, I found some potential problems and fixed them.

Please check with my last commit. If it still doesn't work it should now show you some output, please post it.

4 hours ago, LAbyOne said:

Issues with 5115

 

I'd first ask if anyone has experienced issues with latest Xcode 14

The issue i'm actually having is : impossible boot clover after building 

Xcode 14 maybe sometime in the future, but so far there isn't such release.

You mean 11.4.1? 11.5b1?

 

Did you try to boot osx with verbose?

By the way, in my case the binary posted by @vector sigma boots without any problem.

Edited by Pene
  • Like 1
42 minutes ago, Pene said:

By the way, in my case the binary posted by @vector sigma boots without any problem.

If with gcc works for Him too, may be something goes wrong some where (and some how) in one of the latest commits or happens with one of its themes specifically? @LAbyOne, can you tell me which theme are you using?

20 minutes ago, vector sigma said:

If with gcc works for Him too, may be something goes wrong some where (and some how) in one of the latest commits or happens with one of its themes specifically? @LAbyOne, can you tell me which theme are you using?

But he said it hangs at the Apple Logo. that is after clover already.

Edited by Pene

@vector sigma & @Pene

 

rebuild clover with latest commit and now it boots flawlessly

 

PS. the theme i'm using now is Miele, and loads fine, 

(for a moment i thought could be the fault of so many nude girls it would hang at boot :) lol. ) 

its a homage to Milo Manara (sort of)

Edited by LAbyOne

Hi @Slice @Pene @vector sigma @Jief_Machak

 

I"ve a got a conflict when I try to build latest r5115 commit 64de6d0. How to solve it? Please.

 

Spoiler

Auto-merging rEFIt_UEFI/cpp_unit_test/XString_test.cpp

CONFLICT (content): Merge conflict in rEFIt_UEFI/cpp_unit_test/XString_test.cpp

Auto-merging rEFIt_UEFI/cpp_foundation/XToolsCommon.h

CONFLICT (content): Merge conflict in rEFIt_UEFI/cpp_foundation/XToolsCommon.h

Auto-merging rEFIt_UEFI/cpp_foundation/XStringArray.h

CONFLICT (content): Merge conflict in rEFIt_UEFI/cpp_foundation/XStringArray.h

Auto-merging rEFIt_UEFI/cpp_foundation/XString.h

CONFLICT (content): Merge conflict in rEFIt_UEFI/cpp_foundation/XString.h

Auto-merging rEFIt_UEFI/cpp_foundation/XString.cpp

CONFLICT (content): Merge conflict in rEFIt_UEFI/cpp_foundation/XString.cpp

Auto-merging rEFIt_UEFI/Platform/Posix/stdio.cpp

Auto-merging Xcode/cpp_tests/cpp_tests.xcodeproj/project.pbxproj

CONFLICT (content): Merge conflict in Xcode/cpp_tests/cpp_tests.xcodeproj/project.pbxproj

Auto-merging Xcode/CloverX64/CloverX64.xcodeproj/project.pbxproj

Automatic merge failed; fix conflicts and then commit the result.

 

do a "git checkout rEFIt_UEFI/cpp_unit_test/XString_test.cpp" and then git pull. The conflict on this file should disappear. If yes, do git checkout for the other files.

WARNING : you'll lost any modification you made in these files.

do a "git checkout rEFIt_UEFI/cpp_unit_test/XString_test.cpp" and then git pull. The conflict on this file should disappear. If yes, do git checkout for the other files.

WARNING : you'll lost any modification you made in these files.

 

Or re-clone ?

  • Thanks 1
3 minutes ago, Jief_Machak said:

do a "git checkout rEFIt_UEFI/cpp_unit_test/XString_test.cpp" and then git pull. The conflict on this file should disappear. If yes, do git checkout for the other files.

WARNING : you'll lost any modification you made in these files.

do a "git checkout rEFIt_UEFI/cpp_unit_test/XString_test.cpp" and then git pull. The conflict on this file should disappear. If yes, do git checkout for the other files.

WARNING : you'll lost any modification you made in these files.

 

Or re-clone ?

 

Thanks :) I do not add any modification in these files, so I try your command.

20 hours ago, Sherlocks said:

i'm not test with r5115. but it was success with r5113.

Not for me r5113, r5114, r5115

Failled to load kext on 10.6 ? Only 10.14 and 10.15 no issue

5107 OK Boot correct from Snow to Catalina

Clover mode /ESP Legacy install

Edited by chris1111
5107 OK Boot correct from Snow to Catalina
  • Like 1
38 minutes ago, chris1111 said:

Not for me r5113, r5114, r5115

Failled to load kext ? Only 10.6, 10.14 and 10.15 no issue

5108 OK Boot correct

Clover mode /ESP Legacy install

Provide a boot log with 10.15, maybe we can see something wrong.

If no, you will probably have to be more specific on when it broke. There is too many revisions between 5108 and 5113.

×
×
  • Create New...