Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,059 posts in this topic

Recommended Posts

mnfesq
mnfesq
Posted
Posted
On 11/2/2020 at 3:57 PM, PG7 said:

EliteBook 820 G2

 

intel i5-5300U

intel HD5500 (patch DSDT no fournie)

Wifi Intel AC7265

 

bootloader Clover r5126

install + Boot BigSur Beta 11.0.1 100% OK

 

  Reveal hidden contents

1666534388_Capturedecran2020-11-03a00_56_22.thumb.png.5e923d174d38a8eacd58ff1b07b022b2.png1549637319_IntelWifi.thumb.png.c2d318bf8120201983bf15c33b6bf509.png1988113850_elitebooksystem.thumb.png.06a2efc7316f58eb1f6d6f1181efc8f2.png

 

CLOVER.zip

 

Unfortunately, your Clover files/settings did not work for me.  I had the exact same problem as before.  I am wondering if anyone with a Kabylake-R cpu/chipset has had success with Clover since version 5123.

  • Sad 1
Link to comment
Share on other sites
Guest
Guest
Posted
Posted (edited)

For Clover's lovers :)

An EFI to rule and to boot fine many OS (OS X , Linux, Windows)...

 

Thanks to the Devs for  this and future bugs solving 

 

 

 

Edited by Guest
(OS X , Linux, Windows)...
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
19 hours ago, PG7 said:

Ola 

 

Dell Latitude E6330

intel i7-3520M

intel HD4000

Atheros ar9285

8Go RAM

HDD

 

system test

Clover r5126

 

El Capitan 

Sierra

High Sierra

Mojave

Catalina 

BigSur 

 

install 100% Clover r5126

boot system OK

 

Atheros ar9285 kext = AirPortAtheros40.kext + HS80211Family.kext

 

 

  Reveal hidden contents

1183032188_systemDellLatitudeE6330.thumb.png.0602561812381368242b62d12ef86ba8.png273578349_VarioDellLatitudeE6330.thumb.png.7bf24f3211aab170ee16bed9f50af5cc.png

 

Spoiler

1748687035_ScreenShot2563-11-04at19_23_20.thumb.png.8df3a337d1e774c5201835c5f84b4bb7.png

I want to ask if you lie to me or not.
You said it works for all versions
I can try it, but High_Sierra.
And it doesn't work with bigsur Catalina mojave.
No way:thumbsdown_anim:

  • Confused 1
  • Sad 1
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
18 hours ago, Slice said:

@Jief_Machak

A question to you 


make: *** [/Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/OUTPUT/CLOVERX64.efi] Segmentation fault: 11

I make dirty compilation with old tools and old conf files. So the only problem is DLINK.

Clean compilation leads to same error.

What was crashing GCC, in the end ?

this : 

  //void* memset(void* dst, int ch, UINTN count) __attribute__ ((used));

or the lto flag ?

 

Which version of GCC ? 9 ?

Link to comment
Share on other sites
PG7
PG7
Posted
Posted
55 minutes ago, naiclub said:
  Reveal hidden contents

1748687035_ScreenShot2563-11-04at19_23_20.thumb.png.8df3a337d1e774c5201835c5f84b4bb7.png

I want to ask if you lie to me or not.
You said it works for all versions
I can try it, but High_Sierra.
And it doesn't work with bigsur Catalina mojave.
No way:thumbsdown_anim:

 

Ola 

why should i LIE !!! all prints where the commit has the UUID of the laptop ...

verify that it is not a FAKE! I'm sad about something I test and put the answers and give solutions and people can still DOUBT ....

I do the correction of the DSDT and use all the Patches on it, right I am NOT a Codeur but with years of Hacks and tests I think I can already do many correct tests !!! without you adding an ioreg as well as printing the error at boot in verbose mode and your EFI I can't help! take the DSDT with F4 in the Clover menu.   :no:

  • Like 2
  • Haha 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
2 hours ago, SavageAUS said:

Is there any reason why the main Big Sur volume is back?

 

  Reveal hidden contents

screenshot0.thumb.png.a6e5910528239af179d2d2c6504108eb.png

 

 

  Reveal hidden contents

screenshot1.thumb.png.5721d83f52cdeabc6ac00fc8d429bce3.png

 

 

Because of Big Sur 11.0.1 :) I think a solution will be find soon.

Link to comment
Share on other sites
Guest
Guest
Posted
Posted (edited)

 

 @Jief_Machakwould it be possible to have MMIO values exposed and modifiable (enable/disable I mean) as we have for example for kernel patches or quirks?
 

I mean these:
 

  2022524803_ScreenShot2020-11-04at4_46_25PM.png.c8bda4135f5bc5ab6ec4f8c5e28156ba.png
 

 

Thank you

 

Edited by Guest
Link to comment
Share on other sites
PG7
PG7
Posted
Posted (edited)

@SavageAUS

Is there any reason why the main Big Sur volume is back?

 

bonjour

 

yes,

as Apple changed the version everything will be to redo!

before it was 11 now it is 11.0.1! this happened as soon as it was updated but I didn’t check it because I’m testing between several System and several PC,

The same thing happens with Mojave as it has the Preboot partition and the High Sierra also if it is in APFS,

we have to get that to Jieff and Slice in order to be repaired!

today I am still here testing my Desktop and I already found the solution to be able to install BigSur on it directly,

something that was not leaving after Beta 9 (beta 9 could) I had to disable more security in the bios related to intel and it passes!

 

Google Translate ! 

Edited by PG7
  • Like 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
5 hours ago, Jief_Machak said:

What was crashing GCC, in the end ?

this : 


  //void* memset(void* dst, int ch, UINTN count) __attribute__ ((used));

or the lto flag ?

 

Which version of GCC ? 9 ? 

Supported LTO compression algorithms: zlib
gcc version 10.2.0 (GCC)

LTO optimized codes at link time by erasing non-used procedures. In this case it is memset and attribute((used)) is just ignored.

But I have to comment out this line because of compilation error.

GCC crashes at link time when it encounter a procedure that is already optimized out. The problem is we have very complex system with several stages to compile and link.

I am not fully understanding what is happen here but I encountered in the past with such problems and understood that LTO should be disabled for libraries and protocols while it is very good for main module Cloverx64.efi.

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
2 hours ago, Slice said:

Supported LTO compression algorithms: zlib

gcc version 10.2.0 (GCC)

I have the exact same one, one no seg fault. Compiled fine with lto and attribute used.

 

Could you re-create the error, and compile with V=1 to get all command from makefile to see which exact command failed ?

V is for Verbose. It's a new I've committed recently. Cmd could be : "V=1 ./ebuild.sh {arguments}", or "V=1 ./buildme"

  • Like 1
Link to comment
Share on other sites
stevezheng
stevezheng
Posted
Posted (edited)

@Jief_MachakThank you so much for fixing the USBFixOwnership commit https://github.com/CloverHackyColor/CloverBootloader/commit/5d91bbe25305104192160413b68f94955e7cb03a. It solves my problems, and now I can boot into Mojave & Catalina & Big Sur with no problems ^^. I should notice that earlier since USB Ownership will exactly cause my early boot problem. 

 

Another question: since we use OC to inject kernel extensions, FSInject.efi should be deprecated as it's the legacy Clover kext load efi driver?

Edited by stevezheng
  • Like 1
  • Confused 1
Link to comment
Share on other sites
stevezheng
stevezheng
Posted
Posted
46 minutes ago, maclinuxG4 said:

 

sur ?

I am not sure what do you mean.

 

12 minutes ago, Jief_Machak said:

I don't know what that is. I never used it, even before OC integration, I think.

I found Slice's explanation here. 

It seems FSInject.efi won't be needed anymore for the OC integration.

  • Like 1
Link to comment
Share on other sites
maclinuxG4
maclinuxG4
Posted
Posted (edited)
2 hours ago, Jief_Machak said:

I don't know what that is. I never used it, even before OC integration, I think.

@Jief_Machak

so could talk to slice and check for each driver in UEFI, with OC integration for a list (need / not needed)

 

this list is below, excepted openrutime.efi that is of course need:

ApfsDriverLoader.efi

AppleimageCodec.efi

AppleKeyaggregator.efi

AppelUITheme.efi

AptionInputFix.efi

Fat.efi

firmwarevolume.efi

FSinject.efi

HashServiceFix.efi

PartitionDxe.efi

SMCHelper.efi

UsbKbDxe.efi

VBoxHfs.efi

Edited by maclinuxG4
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
4 hours ago, stevezheng said:

@Jief_MachakThank you so much for fixing the USBFixOwnership commit https://github.com/CloverHackyColor/CloverBootloader/commit/5d91bbe25305104192160413b68f94955e7cb03a. It solves my problems, and now I can boot into Mojave & Catalina & Big Sur with no problems ^^. I should notice that earlier since USB Ownership will exactly cause my early boot problem. 

 

Another question: since we use OC to inject kernel extensions, FSInject.efi should be deprecated as it's the legacy Clover kext load efi driver?

1. I also think that many users report like "5122 works, 5123-5126 no" can be explained by FixUsbOwnership. Thanks Jief.

2. I afraid FSInject.efi was working up to 10.7.5 when we loaded kexts separately from kernel.

  • Like 4
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted (edited)
2 hours ago, Slice said:

"5122 works, 5123-5126 no"

Agreed (it's 5124-5126, because 5123 is still not OC integrated).

 

 

@everyone If you had problems to boot, to boot USB installer, try again with this last commit. CloverX64-5d91bbe-jief.zip

 

3 hours ago, Henry2010 said:

BTW, just asking, do we have to compile 5123 + Fix TgtBridge by ourselves? :)

Release updated : https://github.com/CloverHackyColor/CloverBootloader/releases/tag/5123.1

 

Edited by Jief_Machak
  • Like 4
  • Thanks 1
  • Haha 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
22 hours ago, Jief_Machak said:

I have the exact same one, one no seg fault. Compiled fine with lto and attribute used.

 

Could you re-create the error, and compile with V=1 to get all command from makefile to see which exact command failed ?

V is for Verbose. It's a new I've committed recently. Cmd could be : "V=1 ./ebuild.sh {arguments}", or "V=1 ./buildme"

Reproduced without any problem V=1 ./ebuild.sh -t GCC53

Uncomment line with attribute((used));

Comment out the line with -fno-lto 

"/Users/sergey/src/opt/local/cross/bin/x86_64-clover-linux-gnu-gcc-ar" -cr /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/OUTPUT/CLOVERX64.lib  @/Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/OUTPUT/object_files.lst
[SLINK] CLOVERX64
"/Users/sergey/src/opt/local/cross/bin/x86_64-clover-linux-gnu-gcc" -o /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/DEBUG/CLOVERX64.dll -nostdlib -Wl,-n,-q,--gc-sections,-z,common-page-size=0x40,--defsym=PECOFF_HEADER_SIZE=0x240,--script=/Users/sergey/src/CloverBootloader/BaseTools/Scripts/GccBase.lds,--entry,_ModuleEntryPoint,-u,_ModuleEntryPoint,-Map,/Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/DEBUG/CLOVERX64.map,-melf_x86_64,--oformat=elf64-x86-64,-pie -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror -Wno-array-bounds -ffunction-sections -fdata-sections -include AutoGen.h -fno-common -DSTRING_ARRAY_NAME=CLOVERX64Strings -m64 -fno-stack-protector -mabi=ms "-DEFIAPI=__attribute__((ms_abi))" -maccumulate-outgoing-args -mno-red-zone -Wno-address -mcmodel=small -fpie -fno-asynchronous-unwind-tables -Wno-address -Wno-unused-const-variable -Wno-unused-but-set-variable -Wl,--start-group   @/Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/OUTPUT/static_library_files.lst -Wl,--end-group
"/Users/sergey/src/opt/local/cross/bin/x86_64-clover-linux-gnu-objcopy"  /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/DEBUG/CLOVERX64.dll
[DLINK] CLOVERX64
/Users/sergey/src/opt/local/cross/bin/x86_64-clover-linux-gnu-objcopy --only-keep-debug /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/DEBUG/CLOVERX64.dll /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/DEBUG/CLOVERX64.debug
/Users/sergey/src/opt/local/cross/bin/x86_64-clover-linux-gnu-objcopy  /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/DEBUG/CLOVERX64.dll
cp -f /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/DEBUG/CLOVERX64.debug /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/CLOVERX64.debug
[OBJCOPY] CLOVERX64
"GenFw" -e UEFI_APPLICATION -o /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/OUTPUT/CLOVERX64.efi /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/DEBUG/CLOVERX64.dll
make: *** [/Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/OUTPUT/CLOVERX64.efi] Segmentation fault: 11


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
	/Users/sergey/src/CloverBootloader/rEFIt_UEFI/refit.inf [X64, GCC53, RELEASE]

- Failed -
Build end time: 21:58:29, Nov.05 2020
Build total time: 00:02:17

iMac2017:CloverBootloader sergey$

Try split the problem...

  • Thanks 1
Link to comment
Share on other sites
Guest
Guest
Posted
Posted (edited)

I have updated my rig in signature to Big Sur RC without problem Clover revision: 5126 (master, commit 9e7b4311c)

 

560327565_ScreenShot2020-11-05at9_13_20PM.png.a2f8db724f8eec6dd9483201f5071f38.png

 

Edited by Guest
Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted (edited)
11 hours ago, stevezheng said:

@Jief_MachakThank you so much for fixing the USBFixOwnership commit https://github.com/CloverHackyColor/CloverBootloader/commit/5d91bbe25305104192160413b68f94955e7cb03a. It solves my problems, and now I can boot into Mojave & Catalina & Big Sur with no problems ^^. I should notice that earlier since USB Ownership will exactly cause my early boot problem.

 

Hello @Slice and @Jief_Machak I can also see in the Clover releases list that the last build before OpenCore integration was released as 5123.1:

https://github.com/CloverHackyColor/CloverBootloader/releases/tag/5123.1

 

Again, for those wishing to stay with up to Catalina, this is great help that would keep Clover less complicated to use (I admit I have a hard time understanding the efforts for Big Sur although always appreciative).

 

@Jief_Machak is this build affected by the bug @stevezheng refers to? My Clover config does not use USB's FixOwnership = true and this is the reason I did not detect any bug.

 

Thank you again both for your help, time, and effort and everyone else for contributing!

Edited by MacKonsti
  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...