Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,866 posts in this topic

Recommended Posts

Matgen84
Matgen84
Posted
Posted

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/

post-1110743-0-49617800-1507379614_thumb.png

preboot_CLOVERX64.efi-4243_1013Only.log.zip

preboot_CLOVERX64.efi-4243_OtherOnly.log.zip

Link to comment
Share on other sites
cecekpawon
cecekpawon
Posted
Posted

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

  • Like 2
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

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.

Link to comment
Share on other sites
cecekpawon
cecekpawon
Posted
Posted

Sure you can boot fine with r4223. Slice start to enhance syscls work from r4233. I saw artur_pt doesnt has kexts loaded from "Other" dir. As far as I can remember, "Other" dir designed / should act like 'Common' folder (so Clover should read it no matter what), not just as a fallback when OS ver undetected. So, during test you can put your mandatory kext eg: FakeSMC in "Other" dir, also in OSVer dir for the rest of your kexts, to make sure Clover can read / load / disable em all / each.

  • Like 3
Link to comment
Share on other sites
cecekpawon
cecekpawon
Posted
Posted

since 4239 folder Other case-sentitive

wont boot with lowercase o letter

 

Maybe because of this >>>. Try to change StrStr to StriStr.

 

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

 

IMHO you should ask the developer, he should 'watch' their project to get notified for incoming bug report.

  • Like 1
Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted

Maybe because of this >>>. Try to change StrStr to StriStr.

 

 

IMHO you should ask the developer, he should 'watch' their project to get notified for incoming bug report.

.. and how about this? (has no different for boot though). TIA.  :)

 

 
#EDIT: "CLOVER" but sometimes "Clover".
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

There is no problem. You have two solutions:

1. Update BIOS to newer version.

2. Don't update BIOS. Add Clover Boot Option by second button in low row in Clover GUI. Then sure that you can boot from file /EFI/CLOVER/CLOVERX64.EFI.

Then delete file /EFI/BOOT/BOOTX64.EFI.

Boot options will never propagate any more.

  • Like 1
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Sure you can boot fine with r4223. Slice start to enhance syscls work from r4233. I saw artur_pt doesnt has kexts loaded from "Other" dir. As far as I can remember, "Other" dir designed / should act like 'Common' folder (so Clover should read it no matter what), not just as a fallback when OS ver undetected. So, during test you can put your mandatory kext eg: FakeSMC in "Other" dir, also in OSVer dir for the rest of your kexts, to make sure Clover can read / load / disable em all / each.

 

'Common' folder (so Clover should read it no matter what), not just as a fallback when OS ver undetected.

- i saw this case. lion 10.7.5 app image and use DiskMakerX304 to make usb installer.

then boot 10.7.5 usb installer made by diskmakerx304. then format disk and install. and reboot.

clover can't detect 10.7.5 version(shown null). i check install files. but there are  any version info files in installed disk(to install 10.7.5, 2nd stage).

i used clover r4232. so i have to put fakesmc other folder. then i can install 10.7.5.

ofc restore basesystem.dmg method is no problem. diskmakerx304 method is rare case. but no need restore dmg and package folder.

 

so need to consider other folder with each os version.

also i saw fakesmc 3.4.1 and 3.5.0 difference(old osx support). need to confirm proper combination for old osx.

 

sorry for my bad english.

 

here is evidence

post-980913-0-48755800-1507393100_thumb.png

 

thanks in advance

Link to comment
Share on other sites
cecekpawon
cecekpawon
Posted
Posted (edited)
#EDIT: "CLOVER" but sometimes "Clover".

 

\EFI\CLOVER should be fine.

But azlvda seems to have "other" instead of "Other" kext folder & Clover refused to read em.

 

- i saw this case.

 

Really not sure man, so Clover only read "Other" folder but not your "10.7" folder? Maybe other ppl here like can help you..

*** Maybe your installer SystemVersion.plist is in another place (check your "mac OS X Install Data" / IABootFilesSystemVersion.plist).

Edited by cecekpawon
  • Like 1
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

\EFI\CLOVER should be fine.

But azlvda seems to have "other" instead of "Other" kext folder & Clover refused to read em.

 

 

Really not sure man, so Clover only read "Other" folder but not your "10.7" folder? Maybe other ppl here like can help you..

 

Sorry for bad english.
Right. My mistakes above reply.
 
I have 10.7 with essential kexts. I used each os version folder for boot osx before.
Just found rare case.
 
if i put fakesmc3.5.0 in other folder and fakesmc3.4.1 in 10.7 folder, clover first read other folder and 10.7 folder.
then clover read two fakesmc. So i wonder last loaded fakesmc3.4.1 instead of 3.5.0 when os booting?
Link to comment
Share on other sites
AkimoA
AkimoA
Posted
Posted

Sorry to step into the discussion but may i suggest this ( -nehalem_error_disable ) boot arg being added to Clover / Configurator  ( so people get to know it ) , which i accidently discovered today by digging around AppleTyMCEDriver binary

 

LfazhyB.jpg

 

right hand side top to bottom:

 

 -nehalem_error_disable  disables the AppleTyMCEDriver 

 

offcourse works perfect in 10.13( dunno about older Versions ) and gets rid of the panic on MacPro4,1 and 5,1 at the ECC ram check.

 

Pls ignore this if it is old cheese but i couldnt find anything about it so i thought id share it.

 

And it is a nice addition to the other workarounds to this old little problem.

  • Like 3
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

\EFI\CLOVER should be fine.

But azlvda seems to have "other" instead of "Other" kext folder & Clover refused to read em.

 

 

Really not sure man, so Clover only read "Other" folder but not your "10.7" folder? Maybe other ppl here like can help you..

*** Maybe your installer SystemVersion.plist is in another place (check your "mac OS X Install Data" / IABootFilesSystemVersion.plist).

I remembered old problem with FAT32 driver usually present in UEFI BIOSes.

They may works differently and not as you expected.

Other can be accounted as 8+3 DOS name or as Windows 95 long name and just will not work.

For this case I keep in my drivers64UEFI folder this good driver

Fat-64.efi.zip

but users usually ignore it.

  • Like 2
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

I remembered old problem with FAT32 driver usually present in UEFI BIOSes.

They may works differently and not as you expected.

Other can be accounted as 8+3 DOS name or as Windows 95 long name and just will not work.

For this case I keep in my drivers64UEFI folder this good driver

attachicon.gifFat-64.efi.zip

but users usually ignore it.

I always select this drivers since is release  ;)

Link to comment
Share on other sites
Dr. Hurt
Dr. Hurt
Posted
Posted

0:840  0:000  skipping kext injection (not requested)

0:840  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other

0:840  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.12

 

If kext injection is disabled in plist, why is it scanning/preparing kexts?

I think it should be skipped in this situation thereby saving time and IO. If user forces injection in Clover UI, then scan.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

0:840  0:000  skipping kext injection (not requested)

0:840  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other

0:840  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.12

 

If kext injection is disabled in plist, why is it scanning/preparing kexts?

I think it should be skipped in this situation thereby saving time and IO. If user forces injection in Clover UI, then scan.

There is a contradiction. If you don't want scanning when injection disabled then you will not be able to enable one of them.

So yes, I preferred always scan kexts folders but let user to choose what to inject or not.

Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted

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?

 

@Matgen84,

 

I have a feeling the problem might be due to the XCODE toolchain used to compile Clover.  

 

Can you try booting with the attached r4243 compiled with GCC5.3 in Linux Mint 18.1?

 

As another test, can you also try r4238 with @cecekpawon's changes from post#14767?

r4243_GCC53.zip

  • Like 1
Link to comment
Share on other sites
telepati
telepati
Posted
Posted

Where should I keep my kext after Post installation CLOVER/kexts/other or S/L? Somebody is saying keep it in CLOVER/kexts/other but somebody saying after the post installation move to all kexts to S/L. I really confused where to keep my kexts after post installation?

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Where should I keep my kext after Post installation CLOVER/kexts/other or S/L? Somebody is saying keep it in CLOVER/kexts/other but somebody saying after the post installation move to all kexts to S/L. I really confused where to keep my kexts after post installation?

It is your choice. My opinion that CLOVER/kexts/other  is good for testing and S/L/E is a kexts home where they should live forever and they will appear in cache so will be loaded much faster.

  • Like 2
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

i found one on official r4243.

first i don't have any kext files in others folder and -v bootargs option.

 

just go to Clover Gui, Select High Sierra disk with space bar, go to kext inject management, enter 10.13 folder.

i can see my kexts list. exit 10.13 folder and go other folder, i see there is no kexts files.

exit other folder, then without -v, boot high sierra disk. i can't boot. 

 

i see this " +++++++++++++++++++++++++++++++ "line with apple logo.

 

if -v option, i can boot. strange.

 

 

EDIT1.

i used r4232 version before. there is no problem. i followed same above written process. in syscl's method, kext inject management just located in options.

syscl's kext inject management is perfect working. i tested it.

Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted

On my Skylake rig, if i highlight Sierra drive, press spacebar, select verbose -v then boot macOS with selected options the machine boots like its missing EmuVariableUEFI (Yes i have it) as when the OS loads i have no graphics acceleration etc.. I take it this isn't by design?

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

@Matgen84,

 

I have a feeling the problem might be due to the XCODE toolchain used to compile Clover.  

 

Can you try booting with the attached r4243 compiled with GCC5.3 in Linux Mint 18.1?

 

As another test, can you also try r4238 with @cecekpawon's changes from post#14767?

Hi @fusion71au

 

r4243 compiled with GCC53--------->graphics issue on a part of Clover menu GUI

r4238 patched------------------------->kextd stall AppleACPICPU. Bad getOSVersion: 10.12 instead of 10.13 when booting from High Sierra USB pen drive and Sierra HDD connected

 

I do not have any luck at the moment  :)

 

Edit!  test with release Clover r4233 on SourceForge. Boot from USB 10.13 with HDD Sierra connected:

 

Bad getOSversion : 10.12 instead of 10.13 ----- Other folder inject 3 times. Don't see 10.13 folder for injection. See attached file

preboot_Cloverr4233_USB+HDD-connected.log.zip

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...