Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Guest ricoc90
Guest ricoc90
Posted
Posted

hi guys,

I don't know if this is the right thread, but my question is related with clover, I have not succeed in updating clover the last version is 4239, and yesterday I tried to update clover and the program works and all is installed, but in boot the clover is the same, 4239, anyone knows why?

Thanks in advance 

 

PS: But the install log says 4268, I don't know why this occurs...

 

Most likely there's another Clover installation somewhere on (one of) your disks

MorenoAv
MorenoAv
Posted
Posted

Hi ricoc90,

I only have one other HDD named Time machine and formatted GUID, but don't have clover I think, what should I do?

The update of clover for me is purely cosmetic, until I changed the theme, all the rest all works as it should...

Thanks

fusion71au
fusion71au
Posted
Posted

I have the same issue when it comes to no buildversion detection for macOS (update) installer as well as empty kext inject management, as reported here

(Issue persists in r4278)

 

Can confirm this still happens for App Store upgrade to 10.13.2_17C60c and Clover r4289.  Clover incorrectly identifies "macOS Install Data" as 10.12 instead of 10.13.2...

22:480  0:000  Loading boot.efi  status=Success
22:898  0:418  GetOSVersion: 10.12

It seems the code does not parse "/macOS Install Data/Locked Files/Boot Files/SystemVersion.plist"?

post-846696-0-46169600-1509746013_thumb.png

 

Practically speaking, this means FakeSMC must be placed in Clover/Kexts/Other instead of 10.13, otherwise upgrade will fail.  Also any conditional kext patching in your config.plist eg @SunKi's AppleAHCIPort.kext patch for 10.13 should be made unconditional, otherwise it won't be applied during the update...

22:899  0:000  Filtering KextPatches:
22:899  0:000   - [00]: AppleAHCIPort (External icons patch) :: BinPatch :: [OS: 10.12 | MatchOS: All | MatchBuild: All] ==> allowed
22:899  0:000   - [01]: AppleAHCIPort (fix IO error ICH10 for 10.13, credit SunKi) :: BinPatch :: [OS: 10.12 | MatchOS: 10.13.x | MatchBuild: All] ==> not allowed
22:899  0:000   - [02]: AppleAHCIPort (fix hotplug ICH10 for 10.13, credit SunKi) :: BinPatch :: [OS: 10.12 | MatchOS: 10.13.x | MatchBuild: All] ==> not allowed

Note:  The final, installed system is detected without problems...

 

 

1:358  0:000  Starting Clover revision: 4289 on CLOVER EFI
1:358  0:000  Build with: [Args: -x64 -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_APPLE_HFSPLUS_DRIVER -t XCODE5 | -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.12.6 | XCODE: 9.1]
...
24:496  0:000  Loading boot.efi  status=Success
24:935  0:439  GetOSVersion: 10.13.2 (17C60c)
24:935  0:000  CSR_CFG: CSR_ALLOW_UNTRUSTED_KEXTS | CSR_ALLOW_UNRESTRICTED_FS | CSR_ALLOW_TASK_FOR_PID | CSR_ALLOW_KERNEL_DEBUGGER | CSR_ALLOW_APPLE_INTERNAL | CSR_ALLOW_UNRESTRICTED_DTRACE | CSR_ALLOW_UNRESTRICTED_NVRAM | CSR_ALLOW_DEVICE_CONFIGURATION | CSR_ALLOW_ANY_RECOVERY_
24:935  0:000  Filtering KextPatches:
24:935  0:000   - [00]: AppleAHCIPort (External icons patch) :: BinPatch :: [OS: 10.13.2 | MatchOS: All | MatchBuild: All] ==> allowed
24:935  0:000   - [01]: AppleAHCIPort (fix IO error ICH10 for 10.13, credit SunKi) :: BinPatch :: [OS: 10.13.2 | MatchOS: 10.13.x | MatchBuild: All] ==> allowed
24:935  0:000   - [02]: AppleAHCIPort (fix hotplug ICH10 for 10.13, credit SunKi) :: BinPatch :: [OS: 10.13.2 | MatchOS: 10.13.x | MatchBuild: All] ==> allowed

 

 

preboot_r4289.log.zip

  • Like 3
Badruzeus
Badruzeus
Posted
Posted

r4291 boots 10.13.2 Beta (17C60c) fine on my legacy mach, thanks.  :)

 

 

 

.....  .....  ...
2:734  0:000  Now is 3.11.2017,  22:18:49 (GMT)
2:734  0:000  Starting Clover revision: 4291 on CLOVER EFI
2:734  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.11.6 | XCODE: 8.2]
......  .....  ...
20:805  0:000  Loading boot.efi  status=Success
20:929  0:123  GetOSVersion: 10.13.2 (17C60c)
......  .....  ...
20:956  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
20:956  0:000  Extra kext: EFI\CLOVER\kexts\Other\RealtekRTL8111.kext
20:990  0:034  Extra kext: EFI\CLOVER\kexts\Other\ApplePS2SmartTouchPad.kext
21:027  0:036    |-- PlugIn kext: EFI\CLOVER\kexts\Other\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Keyboard.kext
21:039  0:012    |-- PlugIn kext: EFI\CLOVER\kexts\Other\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Controller.kext
21:048  0:009  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13
21:048  0:000  Extra kext: EFI\CLOVER\kexts\10.13\VoodooBatterySMC.kext
21:083  0:034  Extra kext: EFI\CLOVER\kexts\10.13\FakeSMC.kext
21:096  0:013  Extra kext: EFI\CLOVER\kexts\10.13\IOath3kfrmwr.kext
21:118  0:021  Extra kext: EFI\CLOVER\kexts\10.13\EFICheckDisabler.kext
21:153  0:034  Extra kext: EFI\CLOVER\kexts\10.13\AppleALC.kext
21:178  0:025    |-- PlugIn kext: EFI\CLOVER\kexts\10.13\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
21:437  0:259  Extra kext: EFI\CLOVER\kexts\10.13\CodecCommander.kext
21:504  0:066  Extra kext: EFI\CLOVER\kexts\10.13\CalDigitUSBxHCI.kext
21:521  0:017  Extra kext: EFI\CLOVER\kexts\10.13\CalDigitFastIO.kext
21:550  0:028  Extra kext: EFI\CLOVER\kexts\10.13\AsusNBFnKeys.kext
21:575  0:025  Extra kext: EFI\CLOVER\kexts\10.13\AsusACPIBackLightPanel.kext
21:595  0:019  Extra kext: EFI\CLOVER\kexts\10.13\Lilu.kext
21:614  0:018  SetStartupDiskVolume:
21:614  0:000    * Volume: 'macOS High Sierra'
......  .....  ... 

 

 

bootlog.log.txt_a43sj_r4291.zip

RehabMan
RehabMan
Posted
Posted

Line 405 in /edk2/Clover/rEFIt_UEFI/Platform/platformdata.c

 

- "iMac17,1", "1.0", "C02QFHACGG7L", "iMac-Aluminum",

+ "iMac", "1.0", "C02QFHACGG7L", "iMac-Aluminum",

 

I think this was discussed a while back.  It (mac family) may be that way with the iMac17,1.

Someone should double check on an actual Mac.

TheRacerMaster
TheRacerMaster
Posted
Posted

You can download a IOReg dump from iMac17,1 from here. Search for the "SMBIOS" property (located under AppleSMBIOS). The current family name (iMac17,1) appears to be correct:

Handle 0x0010, DMI type 1, 27 bytes
System Information
	Manufacturer: Apple Inc.
	Product Name: iMac17,1
	Version: 1.0
	Serial Number: C02QH7CZGG7L
	UUID: C35553FC-643B-6152-ACCD-6063A5220F56
	Wake-up Type: Power Switch
	SKU Number:
	Family: iMac17,1
  • Like 4
zxv
zxv
Posted
Posted

You can download a IOReg dump from iMac17,1 from here. Search for the "SMBIOS" property (located under AppleSMBIOS). The current family name (iMac17,1) appears to be correct:

Handle 0x0010, DMI type 1, 27 bytes
System Information
	Manufacturer: Apple Inc.
	Product Name: iMac17,1
	Version: 1.0
	Serial Number: C02QH7CZGG7L
	UUID: C35553FC-643B-6152-ACCD-6063A5220F56
	Wake-up Type: Power Switch
	SKU Number:
	Family: iMac17,1

 

Interesting. Is that the lone exception to the usual pattern?

Matgen84
Matgen84
Posted
Posted

Can confirm this still happens for App Store upgrade to 10.13.2_17C60c and Clover r4289.  Clover incorrectly identifies "macOS Install Data" as 10.12 instead of 10.13.2...

22:480  0:000  Loading boot.efi  status=Success
22:898  0:418  GetOSVersion: 10.12

It seems the code does not parse "/macOS Install Data/Locked Files/Boot Files/SystemVersion.plist"?

attachicon.gifmacOS Install Data.png

 

Practically speaking, this means FakeSMC must be placed in Clover/Kexts/Other instead of 10.13, otherwise upgrade will fail.  Also any conditional kext patching in your config.plist eg @SunKi's AppleAHCIPort.kext patch for 10.13 should be made unconditional, otherwise it won't be applied during the update...

22:899  0:000  Filtering KextPatches:
22:899  0:000   - [00]: AppleAHCIPort (External icons patch) :: BinPatch :: [OS: 10.12 | MatchOS: All | MatchBuild: All] ==> allowed
22:899  0:000   - [01]: AppleAHCIPort (fix IO error ICH10 for 10.13, credit SunKi) :: BinPatch :: [OS: 10.12 | MatchOS: 10.13.x | MatchBuild: All] ==> not allowed
22:899  0:000   - [02]: AppleAHCIPort (fix hotplug ICH10 for 10.13, credit SunKi) :: BinPatch :: [OS: 10.12 | MatchOS: 10.13.x | MatchBuild: All] ==> not allowed

Note:  The final, installed system is detected without problems...

 

 

1:358  0:000  Starting Clover revision: 4289 on CLOVER EFI
1:358  0:000  Build with: [Args: -x64 -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_APPLE_HFSPLUS_DRIVER -t XCODE5 | -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.12.6 | XCODE: 9.1]
...
24:496  0:000  Loading boot.efi  status=Success
24:935  0:439  GetOSVersion: 10.13.2 (17C60c)
24:935  0:000  CSR_CFG: CSR_ALLOW_UNTRUSTED_KEXTS | CSR_ALLOW_UNRESTRICTED_FS | CSR_ALLOW_TASK_FOR_PID | CSR_ALLOW_KERNEL_DEBUGGER | CSR_ALLOW_APPLE_INTERNAL | CSR_ALLOW_UNRESTRICTED_DTRACE | CSR_ALLOW_UNRESTRICTED_NVRAM | CSR_ALLOW_DEVICE_CONFIGURATION | CSR_ALLOW_ANY_RECOVERY_
24:935  0:000  Filtering KextPatches:
24:935  0:000   - [00]: AppleAHCIPort (External icons patch) :: BinPatch :: [OS: 10.13.2 | MatchOS: All | MatchBuild: All] ==> allowed
24:935  0:000   - [01]: AppleAHCIPort (fix IO error ICH10 for 10.13, credit SunKi) :: BinPatch :: [OS: 10.13.2 | MatchOS: 10.13.x | MatchBuild: All] ==> allowed
24:935  0:000   - [02]: AppleAHCIPort (fix hotplug ICH10 for 10.13, credit SunKi) :: BinPatch :: [OS: 10.13.2 | MatchOS: 10.13.x | MatchBuild: All] ==> allowed

 

 

Very good description, I've exactly same issue   :) On my system, Block inject don't show any folder so I can't disabled kext. Fakesmc is in Other Folder and @SunKi's AppleAHCIPort.kext patch for 10.13 is unconditional.

  • Like 2
Slice
Slice
Posted
Posted

Can confirm this still happens for App Store upgrade to 10.13.2_17C60c and Clover r4289.  Clover incorrectly identifies "macOS Install Data" as 10.12 instead of 10.13.2...

22:480  0:000  Loading boot.efi  status=Success
22:898  0:418  GetOSVersion: 10.12

It seems the code does not parse "/macOS Install Data/Locked Files/Boot Files/SystemVersion.plist"?

attachicon.gifmacOS Install Data.png

 

 

Thanks. I accept this in rev 4293.

  • Like 8
MacBart
MacBart
Posted
Posted

Hi, i'm running hackintosh and find something confusing on my system regarding EFI mount device.

The EFI mounts as a random number after each reboot.

In Terminal the number and on Finder just EFI, see below.

 

Can anyone explain or post a link for the reason of this ? I'm just curious.

My apologies for interupting.

As it seems I cant post a screenshot, i'll try to explain.

In Terminal when I ls /volume, I can see my 2 drives and a random number like ctmTempMpINYwUXDBN

In Finder I see my 2 drives and the EFI partition.

Why not EFI in the terminal ?

fusion71au
fusion71au
Posted
Posted

Thanks. I accept this in rev 4293.

 

Thanks Slice.  Clover r4293 correctly detects 10.13.1 or 10.13.2beta updates now.  

 

As an added bonus, it even uses the High Sierra icon for macOS Install of HS ...

 

 

post-846696-0-16741600-1509827100_thumb.png

post-846696-0-31917200-1509827129_thumb.png

post-846696-0-70297100-1509827165_thumb.png

 

 

or Sierra icon for macOS Install of Sierra... :thumbsup_anim:

 

post-846696-0-00752500-1509835235_thumb.png

 

 

 

Thanks for sharing.  The theme folder installer option is missing unless this was on purpose?

 

 

Yes.  I've only attached the Clover "slim" package r4293, without themes, owing to file size restrictions (with themes, it is >10MB).  You can download themes separately with Clover Theme Manager here.

Clover_v2.4k_r4293.pkg.zip

  • Like 3
Ramalama
Ramalama
Posted
Posted

CloverUpdater was not changed since 4000 when it changes 2.3 -> 2.4.

Did you check any other 4xxx revision?

Change AptioFix <-> AptioFix2 or vice versa.

Remove "-v" from boot-args. 

Remove nvram.plist from EFI partition and from Mac root partition.

Slice, Aptiofix or Aptopfix2 doesnt matter, nvram doesnt work...

 

i can write something into nvram (with terminal and sudo nvram....) but on next boot its gone...

Thats the Problem, why im asking...

 

Seems for me, like Aptio maps the wrong Memory region...

 

Cheers

  • Like 1
oSxFr33k
oSxFr33k
Posted
Posted

Thanks Slice.  Clover r4293 correctly detects 10.13.1 or 10.13.2beta updates now.  

 

As an added bonus, it even uses the High Sierra icon for macOS Install of HS ...

 

 

attachicon.gifBoot macOS Install.png

attachicon.gifBlock injected kexts.png

attachicon.gif10.13 detected.png

 

 

or Sierra icon for macOS Install of Sierra... :thumbsup_anim:

 

attachicon.gifBoot macOS Install - Sierra.png

 

 

 

Thanks for sharing.  The theme folder installer option is missing unless this was on purpose?

joevt
joevt
Posted
Posted

Hi, i'm running hackintosh and find something confusing on my system regarding EFI mount device.

The EFI mounts as a random number after each reboot.

In Terminal the number and on Finder just EFI, see below.

 

Can anyone explain or post a link for the reason of this ? I'm just curious.

My apologies for interupting.

As it seems I cant post a screenshot, i'll try to explain.

In Terminal when I ls /volume, I can see my 2 drives and a random number like ctmTempMpINYwUXDBN

In Finder I see my 2 drives and the EFI partition.

Why not EFI in the terminal ?

Mount point names are not the same as volume names. A mount point can be named anything (doesn't need to match the file system volume name) and be anywhere (doesn't need to be in the /Volumes folder). Look at the mount command, and the various file system specific versions like mount_msdos. "diskutil info /dev/disk1s2" will tell you the volume name, mount point name, and device name for partition 2 of disk 1.
Ramalama
Ramalama
Posted
Posted

Nonworking NVRAM is a known issue on newer AptioV boards. Are you using EmuVariableUefi.efi?

 

Yep, ive seen, but there are ways...

1. We can disable SMI Lock in bios (to make things easier)

2. We had same Problems on Aptio4 long time ago but i dont know how it's fixed... (On my Laptop nvram works even with SMI Lock enabled...(Aptio4 Haswell))

 

So there must be a way, there are just not enough benefits, as far as Emulated Nvram exists...

 

In my Opnion, 50% of the Aptiofix driver is useless, if nvram doesnt work.

Thats why i want to get that fixed, but no one want to spend time on this...

 

Cheers

apianti
apianti
Posted
Posted

Your NVRAM breaks because it is being locked by your firmware, this is normal for almost all firmware but you should not have that problem with AptioFix2. Also, you are way off on what the AptioFixes do, with out it you wouldn't even be able to boot. AptioFixes add things Apple firmware expects that UEFI doesn't do, changes ACPI memory page types so they are not moved, and then patches the kernel to properly start and fix the device tree. AptioFix creates a relocation region, loads the kernel there, then moves it to the spot it requested. AptioFix2 tries to give it the region the kernel wants to begin.

 

EDIT: Also maybe try to solve the problem yourself instead of acting like other people should do it for you. I do this because I like to, not because you feel entitled for others working for you without putting in any effort of your own. There are developers who have been doing this for a decade, I myself have for like six or seven years. Do some research, learn, figure the problem out, find the solution. Believe me, no one will do it for you unless they happen to have the same problem. Sometimes, it's the configuration and your firmware settings though, too. But most of the time you need to accept it doesn't work or continue and try to find a way to change it. And just for the record, the NVRAM issue has been known since UEFI booting macOS has been possible, it is an SMI locking problem.

  • Like 8
zxv
zxv
Posted
Posted

Yep, ive seen, but there are ways...

1. We can disable SMI Lock in bios (to make things easier)

2. We had same Problems on Aptio4 long time ago but i dont know how it's fixed... (On my Laptop nvram works even with SMI Lock enabled...(Aptio4 Haswell))

 

So there must be a way, there are just not enough benefits, as far as Emulated Nvram exists...

There's a topic on this if you're so inclined.

mhaeuser
mhaeuser
Posted
Posted

 

 

the NVRAM issue has been known since UEFI booting macOS has been possible, it is an SMI locking problem.

This issue is probably not SMI related, the region is not moved, iirc the SMIs trigger and yet it does not work... A5 has more checks for var names, but I didnt find out what they were supposed to do before I got bored

 

Gesendet von meinem ONEPLUS A5000 mit Tapatalk

  • Like 4
 Share
Go to topic listing
×
×
  • Create New...