Jump to content
30960 posts in this topic

Recommended Posts

13 hours ago, matxpa said:

 

Yes I've already tried it since few days as you could see on this screenshot below (r5155 (2711170) local XCOD8 build)

 

Capturedecran2023-09-01a19_23_39.png.e55b6b618c0529a91d71fc46fe84f330.png

 

So try r5155 without BlockSkywalk in config.plist, with BlockSkywalk activated, with BlockSkywalk deactivated

 

And the reason why i would try this r5155 release is the BCM94360 Wifi card on this Asus Laptop, i suppose it's a legitimate reason.

 

  Reveal hidden contents

Sanstitre.png.91872dfd0eebad07bff8f4fb0672d889.png

 

And to close this topic look in CloverBootloader/rEFIt_UEFI/Settings/ConfigPlist/Config_KernelAndKextPatches.h line code number 318

...

rEFIt_UEFI/Settings/ConfigPlist/Config_KernelAndKextPatches.h:318:    XBool dgetBlockSkywalk() const { return BlockSkywalk.isDefined() ? BlockSkywalk.value() : XBool(true); };

...

Regards

 

 

Hi @matxpa @Slice Thanks a lot. I'm not an expert in code lines, so I don't see that. @matxpa You're right BlockSkywalk should be defined FALSE by default instead of TRUE.

On 9/2/2023 at 3:27 PM, iCanaro said:

@jsl2000 

must be like in the config sample

 

Schermata 2023-09-02 alle 09.25.45.png

Thanks, but legacy Clover 5154/5155 got KP at Sonoma and no such an issue at Ventura in B85M-G hackintosh.

[Partially Solved]

1. This key should be true instead of False for my B85M-G hackintosh.

2. OpenCore can enable BCM4352 WiFi adapter now, but Clover still failed to connect any WiFi hub/port.

Screenshot 2023-09-03 at 10.16.47 AM.png

Screenshot 2023-09-03 at 10.08.18 PM.png

Edited by jsl2000
  • Like 1
17 hours ago, cankiulascmnfye said:

The latest beta build does not work for me. I get the following error:

 

20230903_083819_HDR.thumb.jpg.3784d2d016b36b85e79edb22f502da0e.jpg

 

Previous build works fine (check log for reference)

bootlog_5154.txt 52.65 kB · 3 downloads

After set BlockSkywalk key from False to True my B85M-G hackintosh got the same error as yours.

1 hour ago, cankiulascmnfye said:

 

I did that. It does not work. Same error

 

Do use CloverPKG to update ? Or only copy/past BOOTX64 and CLOVERX64 ?

For my part, I use an EFI folder on the desktop to update the two Clover files . Then I mount the ESP partion, delete the existing EFI folder and empty the trash. Finally, I copy the desktop folder to the EFI partition.
Because sometimes I have the same problem as you.

 

 

6 hours ago, Matgen84 said:

 

Do use CloverPKG to update ? Or only copy/past BOOTX64 and CLOVERX64 ?

For my part, I use an EFI folder on the desktop to update the two Clover files . Then I mount the ESP partion, delete the existing EFI folder and empty the trash. Finally, I copy the desktop folder to the EFI partition.
Because sometimes I have the same problem as you.

 

 

 

I update it manually. I don't use Clover on my system's ESP I use a USB flash drive just for testing. I don't see how deleting the EFI folder could resolve issues seemingly related to Clover's way of handling Kernel Collections… weird

On 9/1/2023 at 8:32 PM, matxpa said:

 

Yes I've already tried it since few days as you could see on this screenshot below (r5155 (2711170) local XCOD8 build)

 

Capturedecran2023-09-01a19_23_39.png.e55b6b618c0529a91d71fc46fe84f330.png

 

So try r5155 without BlockSkywalk in config.plist, with BlockSkywalk activated, with BlockSkywalk deactivated

 

And the reason why i would try this r5155 release is the BCM94360 Wifi card on this Asus Laptop, i suppose it's a legitimate reason.

 

  Reveal hidden contents

 

And to close this topic look in CloverBootloader/rEFIt_UEFI/Settings/ConfigPlist/Config_KernelAndKextPatches.h line code number 318

...

rEFIt_UEFI/Settings/ConfigPlist/Config_KernelAndKextPatches.h:318:    XBool dgetBlockSkywalk() const { return BlockSkywalk.isDefined() ? BlockSkywalk.value() : XBool(true); };

...

Regards

 

As I see it is better to set "false" by default?

  • Like 2
12 hours ago, cankiulascmnfye said:

 

I update it manually. I don't use Clover on my system's ESP I use a USB flash drive just for testing. I don't see how deleting the EFI folder could resolve issues seemingly related to Clover's way of handling Kernel Collections… weird

 

Because sometimes, I have a bad behavior if I copy directly to ESP, BOOTX64 and CLOVERX64 files.

On 9/5/2023 at 4:23 AM, Slice said:

As I see it is better to set "false" by default?

In my M5A hackintosh I can boot Sonoma beta 7 by legacy Clover 5154 with BlockSkywalk=False.

If it's True I'll get KP (unable to kext scan) during booting.

But in B85M-G hackintosh I got different results which bothered me up to now !

Screenshot 2023-09-06 at 20.41.37.png

  • Like 3

Hi @Slice

 

I can't build latest commit 0ea0020 (Monterey 12.6.8/XCode 14.3)

 

Spoiler

CC] UefiShellInstall1CommandsLib
[CC] CopyMemWrapper
[CC] ModU64x32
/Users/mathieu/src/Cloverbootloader/UefiCpuPkg/Library/BaseXApicLib/BaseXApicLib.c:267:3: error: variable '__DebugCodeLocal' set but not used [-Werror,-Wunused-but-set-variable]
  DEBUG_CODE (
  ^
/Users/mathieu/src/Cloverbootloader/MdePkg/Include/Library/DebugLib.h:566:3: note: expanded from macro 'DEBUG_CODE'
  DEBUG_CODE_BEGIN ();          \
  ^
/Users/mathieu/src/Cloverbootloader/MdePkg/Include/Library/DebugLib.h:542:68: note: expanded from macro 'DEBUG_CODE_BEGIN'
#define DEBUG_CODE_BEGIN()  do { if (DebugCodeEnabled ()) { UINT8  __DebugCodeLocal
                                                                   ^
1 error generated.
make: *** [/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8/X64/UefiCpuPkg/Library/BaseXApicLib/BaseXApicLib/OUTPUT/BaseXApicLib.obj] Error 1


build.py...
 : error 7000: Failed to execute command
    make tbuild [/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8/X64/UefiCpuPkg/Library/BaseXApicLib/BaseXApicLib]

 

16 minutes ago, Matgen84 said:

Hi @Slice

 

I can't build latest commit 0ea0020 (Monterey 12.6.8/XCode 14.3)

 

  Hide contents

CC] UefiShellInstall1CommandsLib
[CC] CopyMemWrapper
[CC] ModU64x32
/Users/mathieu/src/Cloverbootloader/UefiCpuPkg/Library/BaseXApicLib/BaseXApicLib.c:267:3: error: variable '__DebugCodeLocal' set but not used [-Werror,-Wunused-but-set-variable]
  DEBUG_CODE (
  ^
/Users/mathieu/src/Cloverbootloader/MdePkg/Include/Library/DebugLib.h:566:3: note: expanded from macro 'DEBUG_CODE'
  DEBUG_CODE_BEGIN ();          \
  ^
/Users/mathieu/src/Cloverbootloader/MdePkg/Include/Library/DebugLib.h:542:68: note: expanded from macro 'DEBUG_CODE_BEGIN'
#define DEBUG_CODE_BEGIN()  do { if (DebugCodeEnabled ()) { UINT8  __DebugCodeLocal
                                                                   ^
1 error generated.
make: *** [/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8/X64/UefiCpuPkg/Library/BaseXApicLib/BaseXApicLib/OUTPUT/BaseXApicLib.obj] Error 1


build.py...
 : error 7000: Failed to execute command
    make tbuild [/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8/X64/UefiCpuPkg/Library/BaseXApicLib/BaseXApicLib]

 

Choose XCODE14 instead of XCODE8.

  • Thanks 1

@SliceIs it possible to declare in clover bootloader the kext order like it is possible to do in opencore

In clover bootloader i cant enable my Broadcom wifi in Sonoma adding the required kext and the bootarg (also disabling sip is a mandatory condition)

mandatory steps are in Opencore

secureboot disabled (ok also in clover)

disabling sip (ok also in clover)

bootarg amfi=0x80 (ok also in clover)

block com.apple.iokit.IOSkywalkFamily (no sure it is ok in clover

kexts order:

IOSkywalkFamily.kext

IO80211FamilyLegacy.kext

IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext

(i put them in kexts/14 folder but i cant give the same opencore order)

 

any advice or info to be able to use this wifi also in your bootloader?

thank you

 

edit Clover log:

 

 

2023-09-08_06-46_CLOVERX64.efi.log

Edited by mariosun
clover log
  • Sad 1

@Slice in latest commit fcead07

is there a particular reason for commenting out make nvram2 ?

Ask this because it make the build process fail when choosing

make pkg, build all or make Release

 

	[CXX] nvram2
#@cc -o nvram2 nvram2.c -framework CoreFoundation -framework IOKit -Wall >/dev/null
mv: rename nvram2 to /Users/labyone/src/CloverBootloader/CloverPackage/sym/utils/nvram2: No such file or directory
make[2]: *** [/Users/labyone/src/CloverBootloader/CloverPackage/sym/utils/nvram2] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [pkg] Error 2
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

 

20 hours ago, LAbyOne said:

@Slice in latest commit fcead07

is there a particular reason for commenting out make nvram2 ?

Ask this because it make the build process fail when choosing

make pkg, build all or make Release

 

	[CXX] nvram2
#@cc -o nvram2 nvram2.c -framework CoreFoundation -framework IOKit -Wall >/dev/null
mv: rename nvram2 to /Users/labyone/src/CloverBootloader/CloverPackage/sym/utils/nvram2: No such file or directory
make[2]: *** [/Users/labyone/src/CloverBootloader/CloverPackage/sym/utils/nvram2] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [pkg] Error 2
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

 

Fixed.

The reason is a long story. Look carefully.

When I compiled an utility (nvram2 for example) in Ventura using Clang from Xcode 14 I got a good working utility in Ventura. But... it will not work in Mojave.

I don't know what is changed but universal working utility can be created in Mojave using Clang from Xcode 11. It will work in Mojave and in Ventura.

So to create an Clover release I have to replace nvram2 utility by the one compiled under Mojave.

Have you any thought about the issue?

12 minutes ago, Matgen84 said:

Hi @Slice

I can't build Clover (Monterey 12.6.8, XCODE 14,3) Toolchain=XCODE14; Python 3.11.5

 

 

Clover_Build.log 2.88 kB · 0 downloads

Delete folder Build and try again.

  • Thanks 1
5 hours ago, Slice said:

The reason is a long story. Look carefully.

When I compiled an utility (nvram2 for example) in Ventura using Clang from Xcode 14 I got a good working utility in Ventura. But... it will not work in Mojave.

I don't know what is changed but universal working utility can be created in Mojave using Clang from Xcode 11. It will work in Mojave and in Ventura.

So to create an Clover release I have to replace nvram2 utility by the one compiled under Mojave.

Have you any thought about the issue?

 

As it is now, building any tool related to the running system (hence supported xcode version)

will work when used running the same or newer system version, but fail when used on older,  just as you reported.

And any user building from source should have no problem, using it, if on the same or newer system, in legacy boot.

 

But also many user get Clover installer from repo archive,

and the only solution I can think of is :

To have it working on any system it should be built on the older one (you have) and stored as archive in the root of the repo.

then installed from within it into Utils folder (and eventually into the pkg)

 

 

The Release version Should have it in this section on the installer

and eventually installed into /usr/local (as was for ccpv)

ScreenShot.png.644a9b0fa94d2dde12db1bb79d55df73.png

 

( I still have a 10.13.6 running in case you want to test it built an older system)

 

OR

maybe if possible adding to the project some CFLAGS could solve?

CC=clang CFLAGS="-mmacosx-version-min=10.xxx
  LDFLAGS="-mmacosx-version-min=10.xxx" 

 

×
×
  • Create New...