Jump to content

Clover General discussion


ErmaC
29,869 posts in this topic

Recommended Posts

18 minutes ago, yapan4 said:

Hey guys, please remind me the correct set of commands for git clone. Thanks.

 

git clone --recurse-submodules "https://github.com/CloverHackyColor/CloverBootloader.git" "DESTINATION_PATH" :)

Of course, replace "DESTINATION_PATH" by your own location.

5 minutes ago, Jief_Machak said:

Oups, forgot that one... Must have been very late when I made it ;)


Hi @Jief_Machak Where we can find Xcode/CloverConfigPlistValidator ? It's a good idea  to integrate this tool in buildme and in the CloverPackage

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

50 minutes ago, yapan4 said:

Hey guys, please remind me the correct set of commands for clone from master. Thanks.

I do the follow

cd ~
mkdir src
cd src
git clone https://github.com/CloverHackyColor/CloverBootloader.git
cd CloverBootloader
git clone https://github.com/CloverHackyColor/OpenCorePkg.git
./buildme

 

  • Like 3
  • Thanks 1
Link to comment
Share on other sites

This is simpler with the same result

cd ~
mkdir src
cd src
git clone --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git
cd CloverBootloader
./buildme

 

  • Like 4
  • Thanks 1
Link to comment
Share on other sites

You can also :

git submodule foreach --recursive git clean -d -f -f -x
git clean -d -f -f -x
git submodule foreach git checkout master
git checkout master
git reset --hard --recurse-submodules

this will restore the repo in the exact same state as if it were freshly cloned. Only difference is that it doesn't need to re-download.

Edited by Jief_Machak
  • Thanks 1
Link to comment
Share on other sites

1 hour ago, eng_redaesm said:

seems to work good but i have these messages on screen 

 

WhatsApp Image 2021-04-29 at 11.13.59 AM.jpeg

Yes, it's a way for me to know where it crashes when it crashes before being able to save the log.

 

Unfortunately, my compilation works, but not yours.

So, edit the file main.cpp, line 2685. Change

//#define DEBUG_ERALY_CRASH

by

#define DEBUG_ERALY_CRASH

compile and try.

  • Like 1
Link to comment
Share on other sites

1 minute ago, Jief_Machak said:

Yes, it's a way for me to know where it crashes when it crashes before being able to save the log.

 

Unfortunately, my compilation works, but not yours.

So, edit the file main.cpp, line 2685. Change


//#define DEBUG_ERALY_CRASH

by


#define DEBUG_ERALY_CRASH

compile and try.

i will try and inform you

Link to comment
Share on other sites

1 hour ago, MifJpn said:

@Jief_Machak

I'm not very familiar with it, so I'm sorry.
Is it like the following

% pwd
/Users/alpha/CloverBootloader/Xcode/CloverConfigPlistValidator

% xcodebuild -scheme CloverConfigPlistValidator_Release > error.txt

Thank you for your cooperation.

error.txt 387.15 kB · 5 downloads

The error

In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/usr/include/libkern/_OSByteOrder.h:80:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk/usr/include/libkern/arm/OSByteOrder.h:91:2: error: unknown type name 'uintptr_t'; did you mean 'intptr_t'?
        uintptr_t       _offset
        ^

Why arm?

Looks like Xcode bug.

Link to comment
Share on other sites

2 hours ago, MifJpn said:

@Jief_Machak

I'm not very familiar with it, so I'm sorry.
Is it like the following

% pwd
/Users/alpha/CloverBootloader/Xcode/CloverConfigPlistValidator

% xcodebuild -scheme CloverConfigPlistValidator_Release > error.txt

Thank you for your cooperation.

error.txt 387.15 kB · 6 downloads


Can't build too (Xcode 11.3.1 - Mojave): CloverConfigPlistValidator_Release

In file included from <built-in>:1:
/Users/mathieu/src/Cloverbootloader/rEFIT_UEFI/PlatformPOSIX/include/Platform.h:104:10: fatal error: '../../Build/Clover/DEBUGMACOS_XCODE8/X64/rEFIt_UEFI/refit/DEBUG/AutoGen.h' file not found
#include "../../Build/Clover/DEBUGMACOS_XCODE8/X64/rEFIt_UEFI/refit/DEBUG/AutoGen.h"

 

error.txt

Link to comment
Share on other sites

18 hours ago, Jief_Machak said:

So you can now compile the validator yourself : just go to Xcode/CloverConfigPlistValidator and open the xcode project. Compile the scheme "CloverConfigPlistValidator_Release" and voila.

Is there someone up to integrate this in buildme and in the CloverPackage ?

No such file

#include "../../Build/Clover/DEBUGMACOS_XCODE8/X64/rEFIt_UEFI/refit/DEBUG/AutoGen.h"

 

  • Like 1
Link to comment
Share on other sites

5 hours ago, Jief_Machak said:

Yes, it's a way for me to know where it crashes when it crashes before being able to save the log.

 

Unfortunately, my compilation works, but not yours.

So, edit the file main.cpp, line 2685. Change


//#define DEBUG_ERALY_CRASH

by


#define DEBUG_ERALY_CRASH

compile and try.

i did as you said  i got only the messages  and no boot screen 

WhatsApp Image 2021-04-29 at 6.29.44 PM.jpeg

Link to comment
Share on other sites

error: Build input file cannot be found: '/Users/sergey/src/CloverBootloader/PosixCompilation/DEBUG_Libs/Autogen/AutoGen.c' (in target 'CloverConfigPlistValidator' from project 'CloverConfigPlistValidator')

There are symbolic links to milk.

Link to comment
Share on other sites

I should not need AutoGen.c for the validator. And it should not be DEBUG_Libs. And I should even not need DEBUG_Libs...

This project is based on an other project where I compile all Clover and all its library as a mac command line application. Probably left over things in the xcode project.

I'll fix that.

1 hour ago, eng_redaesm said:

i did as you said  i got only the messages  and no boot screen 

WhatsApp Image 2021-04-29 at 6.29.44 PM.jpeg

If you get step 6, you should get a debug log.

Do you have it ?

  • Like 2
Link to comment
Share on other sites

8 hours ago, Jief_Machak said:

Could you try this CLOVERX64.efi.zip ?

this version went on to boot up. it doesn't like the key NewWay_80000000

tluck@Test-Mac ~/Downloads

$ ./CloverConfigPlistValidator0.8

Error: Unexpected tag 'true' at line 15 col 31. Was expecting <key>.

Warning: Unknown key '/Boot/IgnoreNVRAMBoot:74'. Skipped.

Warning: Unknown key '/Boot/UseAlternateLogo:82'. Skipped.

Warning: Unknown key '/GUI/Mouse/DoubleClick:284'. Skipped.

Warning: Unknown key '/Graphics/EDID/Comment:317'. Skipped.

Warning: Unknown key '/Quirks/AppleCpuPmCfgLock:471'. Skipped.

Warning: Unknown key '/Quirks/AppleXcpmCfgLock:474'. Skipped.

Warning: Unknown key '/Quirks/CustomSMBIOSGuid:481'. Skipped.

Warning: Unknown key '/Quirks/DisableRtcChecksum:489'. Skipped.

Warning: Unknown key '/Quirks/LapicKernelPanic:513'. Skipped.

Warning: Unknown key '/Quirks/PanicNoKextDump:516'. Skipped.

Warning: Unknown key '/Quirks/ProvideConsoleGopEnable:525'. Skipped.

 

tluck@Test-Mac ~/Downloads

$ more config-nowarning-noerror.plist

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

        <key>ACPI</key>

        <dict>

                <key>DSDT</key>

                <dict>

                        <key>Debug</key>

                        <true/>

                        <key>Fixes</key>

                        <dict>

                                <key>FixRegions_10000000</key>

                                <true/>

                                <key>NewWay_80000000</key>

                                <true/>

                        </dict>

                        <key>Name</key>

                        <string>DSDT.aml</string>

                </dict>

Link to comment
Share on other sites

1 hour ago, tluck said:

this version went on to boot up. it doesn't like the key NewWay_80000000

 

The key is no more exists.

 

Anyway I see no reason to delete non-existent keys. Clover will not read keys that it doesn't know. (opposite to OC).

The key may be intended for other Clover version, for example.

  • Like 2
Link to comment
Share on other sites

×
×
  • Create New...