Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

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
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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
Link to comment
Share on other sites

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
Link to comment
Share on other sites

@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
Link to comment
Share on other sites

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.

 

Link to comment
Share on other sites

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
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

1 hour 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

 

sorry. my remember is mistake.

maybe it would be between r5108~r5100

  • Like 1
Link to comment
Share on other sites

8 hours ago, Pene said:

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.

Thanks 

I don't know if its relate to Clover or my Snow leopard SSD because I have some trouble recently

 

This is my test PC for Beta and Graphics

 

Edited by chris1111
deleted log
Link to comment
Share on other sites

5 hours ago, chris1111 said:

Thanks 

I don't know if its relate to Clover or my Snow leopard SSD because I have some trouble recently

 

This is my test PC for Beta and Graphics

bdmesg Output.txt.zip

I don't see something wrong there, but it doesn't mean there isn't a problem. However, being Snow Leopard it's going to be very hard to check or reproduce.

Link to comment
Share on other sites

1 hour ago, Pene said:

I don't see something wrong there, but it doesn't mean there isn't a problem. However, being Snow Leopard it's going to be very hard to check or reproduce.

Yes I know

for now  I don't have issue with r5097 its hard to try all above revision 

Link to comment
Share on other sites

43 minutes ago, chris1111 said:

Yes I know

for now  I don't have issue with r5097 its hard to try all above revision 

Yes, obviously. But we would kinda need to know which revision breaks it, to be able to inspect what broke it (without being able to test).

 

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...