Clover General discussion

chris1111 · October 6, 2017

Clover 4221 10.6/10.7/10.12/10.13

No issue kext inject

Slice · October 6, 2017

Sorry for my bad english

I forgot to say that my Sierra HDD was connected. After select USB by F8 for booting, I try r4239 with USB installer.

I don't understand your answer. what is the correct procedure in this case for testing?

I just see no issues in your observations.

You started 10.12 and don't see 10.13. It is OK (All Correct).

Hi Slice,

Another test: Clover r4241 on HDD macOS 10.13.1 with HDD Sierra connected.

When I boot from macOS 10.13.1----->No injection (10.13 folder only). r4241. Kext management don't see empty folder (10.6, 10.7, etc)

When I boot from macOS 10.13.1----->Ok (10.13 folder only), r4233. Kext management see all empty folder (10.6, 10.7, etc)

This is a difference between old and new Clover. You need no to see 10.6 folder if you boot 10.13.1.

syscl · October 6, 2017

I just see no issues in your observations.

You started 10.12 and don't see 10.13. It is OK (All Correct).

This is a difference between old and new Clover. You need no to see 10.6 folder if you boot 10.13.1.

Slice, why no init InjectKextList for all folder then list kext for current system, then it will never fail inject kext even if user see 10.6 then boot 10.13?

syscl

fusion71au · October 6, 2017

When I boot from macOS 10.13.1----->No injection (10.13 folder only). r4241. Kext management don't see empty folder (10.6, 10.7, etc)

@Matgen84,

From your boot log

90:535  0:026  GetOSVersion: 10.13.1 (17B25c)
90:842  0:000  Beginning FSInjection
90:842  0:000  skipping kext injection (not requested)

Check your config.plist/SystemParameters/InjectKexts set to Yes or Detect?

	<key>SystemParameters</key>
	<dict>
		<key>InjectKexts</key>
		<string>Yes</string>
	</dict>

Hmmb, sounds strange. I was also using r4239 under 10.13.1 (17B25C) but got no problem with Slice's FakeSMC (v3.5.0) & RealtekRTL8111 (v2.2.1).

Is there any unresolved patch when U were compiling r4239 binary using buildclover script? (I don't think so, though)

(I attached my compiled r4239 below, thanks).

It is impossible for unknown arch=.

I may propose that your compilation is buggy. What is your toolchain?

I think I compiled r4239 (XCODE 8.3.3 in 10.13, toolchain setting XCODE8) forgetting to revert @cecekpawon's diff patch from r4238...

4:038  0:000  Build with: [Args: -x64 -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_APPLE_HFSPLUS_DRIVER -t XCODE8 | -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.13 | XCODE: 8.3.3]

After deleting & re-downloading Clover r4241 from svn, everything OK again. Clover r4241 boots successfully into 10.13.1beta and kexts detected in /10.xx & /Other.

Compiled with XCODE 8.2.1 in 10.11.6, toolchain setting XCODE8 ---> boots fine into 10.13.1beta, 10.13, 10.12.6, 10.7

Compiled with XCODE 9.0 in 10.13.1beta, toolchain setting XCODE8 ---> boots fine into 10.13.1beta, 10.13, 10.12.6, 10.7

Thanks everyone for helping with troubleshooting .

Boot logs.zip

Clover_v2.4k_r4241.zip

telepati · October 6, 2017

Guys why EmuVariableUefi-64.efi affect the update process? When I try to update supplemental update I am getting this error;

But when I remove the EmuVariableUefi-64.efi I can update without any problem.

SavageAUS · October 7, 2017

Guys why EmuVariableUefi-64.efi affect the update process? When I try to update supplemental update I am getting this error;

error-install.png

But when I remove the EmuVariableUefi-64.efi I can update without any problem.

I dont even have EmuVariableUEFI on my laptop and im getting that error.

cyrhex · October 7, 2017

@slice can i have ur fakesmc 3.5 coz other user says using this version of fakesmc bypass the osinstall.mpkg damage error installing high sierra using clover uefi,,TIA

bronxteck · October 7, 2017

the link is in his signature HWsensors3

Matgen84 · October 7, 2017

@Matgen84,

From your boot log
90:535  0:026  GetOSVersion: 10.13.1 (17B25c)
90:842  0:000  Beginning FSInjection
90:842  0:000  skipping kext injection (not requested) 
Check your config.plist/SystemParameters/InjectKexts set to Yes or Detect?

I install r4241 in update mode. Config.plist work well if I downgrade to r4223 with EFI Backups, for example.

I just see no issues in your observations.

You started 10.12 and don't see 10.13. It is OK (All Correct).

This is Test r4239 from USB pendrive with HDD Sierra connected: I started 10.13. GetOSversion detected 10.12. Only Other folder in pendrive, boot High Sierra.

Sorry for my english.

Slice · October 7, 2017

Slice, why no init InjectKextList for all folder then list kext for current system, then it will never fail inject kext even if user see 10.6 then boot 10.13?

syscl

You should realise the process of menu creation and running. There are two different process.

If we set Init InjectKextList into menu creation then it will be added with every menu entries that we already saw as double injection.

I can set the init conditionally if not inited yet.

Slice · October 7, 2017

For those who have a problem with kext injection please test my version

CLOVERX64.efi-4243.zip

azlvda · October 7, 2017

since 4239 folder Other case-sentitive

wont boot with lowercase o letter

Badruzeus · October 7, 2017

For those who have a problem with kext injection please test my version

CLOVERX64.efi-4243.zip

Ah, forgot to mention that my prev tests were using "InjectKexts=Yes", now with "...=Detect" ur r4243 boots 10.13.1 (17B25c) fine from "/kexts/10.13" folder, also same result with manually buildclover script for r4243.

And how could we figure out that gotta "kext injection problem"..? Thanks.

bootlog.log_r4243_slice.txt.zip

bootlog.log_r4243_buildclover.txt.zip

Matgen84 · October 7, 2017

For those who have a problem with kext injection please test my version

CLOVERX64.efi-4243.zip

Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.12 when I boot from USB pen drive (10.13 only) and HDD Sierra connected: Kextd stall on AppleACPICPU and black screen

Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.13.1 when I boot from HDD High Sierra (10.13 only) and HDD Sierra connected. Kextd stall on AppleACPICPU

Commits r4243 HDD 10.13.1 alone (10.13 folder only): with or without CloverX64.efi-4243: No Injection -----> "Thinning failed" error.

Here, new kext management don't work with 10.13 folder only

I don't understand why these issues?

preboot_Clover_r4243_USB.log.zip

preboot_Cloverr4243_HDD_alone.log.zip

artur_pt · October 7, 2017

hello Slice

for me is working good

boot.log.zip

thanks

Slice · October 7, 2017

Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.12 when I boot from USB pen drive (10.13 only) and HDD Sierra connected: Kextd stall on AppleACPICPU and black screen

Commits r4243: with or with without CloverX64.efi-4243, Clover get OSversion 10.13.1 when I boot from HDD High Sierra connected. Kextd stall on AppleACPICPU

Commits r4243 HDD 10.13.1 alone (10.13 folder only): with CloverX64.efi-4243: No Injection -----> "Thinning failed" error. I don't test without CloverX64.efi-4243

I don't understand why these issues?

Both logs with NOT MY clover.

Matgen84 · October 7, 2017

Both logs with NOT MY clover.

Forgot when I have edited my previous post. Can you look it. Please

New attached files here with your cloverX64.

preboot_Clover_r4243_HDD_newCloverX64.log.zip

Slice · October 7, 2017

Forgot when I have edited my previous post. Can you look it. Please

New attached files here with your cloverX64.

No, it is not my Clover.

cecekpawon · October 7, 2017

___Matgen84___

mv CLOVERX64.efi to \EFI\BOOT\BOOTX64.efi ?

phi777 · October 7, 2017

~~I've got a dumb question, but could this be a clover problem? https://github.com/Piker-Alpha/HandyScripts/issues/7~~

EDIT: already fixed

Matgen84 · October 7, 2017

Both logs with NOT MY clover.

For testing, I replace cloverX64.efi compiled by your clover. Good or bad use? I re-download your cloverx64.efi-4243 and try again.

___Matgen84___

mv CLOVERX64.efi to \EFI\BOOT\BOOTX64.efi ?

what version: original or new slice's cloverx64.efi-4243? CloverX64 will be the same version in /EFI/BOOT/ and /EFI/Clover. I suppose? Thanks

Edit: with CLOVERX64.efi-4243 - 10.13 Only --->Injection but kext stall AppleACICPU, black screen with pointer

with CLOVERX64.efi-4243 - Other Only---> Failed injection with kext stall AppleACICPU....

I put Slice's CloverX64: in /EFI/Clover and renamed it to BOOTX64 before put it /EFI/BOOT/

preboot_CLOVERX64.efi-4243_1013Only.log.zip

preboot_CLOVERX64.efi-4243_OtherOnly.log.zip

qqcapcom · October 7, 2017

I have this problem, could anyone help me?

http://www.insanelymac.com/forum/topic/309280-too-many-random-boot-options-available-in-bios-boot-options-for-gigabyte-z170x-ud5-after-installation-of-elcapitan-10111/

cecekpawon · October 7, 2017

Slice test version should contain: "Args: -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.11.6 | XCODE: 7.3.1".
Yes, \EFI\Clover\CLOVERX64.efi should be same with \EFI\BOOT\BOOTX64.efi
To check your Clover path / booted from:
0:100 0:000 SelfDevicePath=PciRoot(0x0)...
0:100 0:000 SelfDirPath = \EFI\BOOT

Matgen84 · October 7, 2017

Slice test version should contain: "Args: -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.11.6 | XCODE: 7.3.1".

Yes, \EFI\Clover\CLOVERX64.efi should be same with \EFI\BOOT\BOOTX64.efi

To check your Clover path / booted from:

0:100 0:000 SelfDevicePath=PciRoot(0x0)...

0:100 0:000 SelfDirPath = \EFI\BOOT

Thanks @cecekpawon

Attached preboot files in post #14809 are correct. But r4243 don't work in my system despite Slice test version. Downgrade to 4223 version, my system work.

magnifico · October 7, 2017

No, it is not my Clover.

????? sorry, the problem then who is it? Are there developers who make mistakes? Only curiosity :angel: :angel:

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites