Clover General discussion

nikitenich · January 12, 2018

Question:

I saw at around 750 page that you where talking about patches for Pentium and integrate them directly into Clover version 41xx. Does that happend ? I am asking because I have 2 patches in my config.plist made by vit9696 and Sherlocks and I wanna know if I can remove them or not:

Find: b9a00100 000f32

Replace: b9a00100 0031c0

Find: 89d804c4 3c22

Replace: 89d804c6 3c22

I have the Pentium G3220.

These patches in clover:

#1

#2

Use KernelXCPM key in KernelAndKextPatches.

maxb2000 · January 12, 2018

These patches in clover:

#1

#2

Use KernelXCPM key in KernelAndKextPatches.

Thank you ! I deleted the kernel patches and it's working !

Anyway can somebody take a look on my DSDT and other stuff ? I am asking because the sound via HDMI works only after sleep. Like after sleep the sound works but before it doesn't...

https://drive.google.com/open?id=18YGCj5Z3j8cehMOChGtckap0uWmQ6tjA

RehabMan · January 12, 2018

@apianti

Tested new OsxAptioFix2Drv-64.efi on my NUC6 Skull Canyon (NUC6i7KYK) with 10.13.2.

Tested by merging in changes to my own Clover fork.

It booted no problem and was able to eliminate EmuVariableUefi-64.efi and still have working NVRAM.

Will test on other computers in the coming days.

But since the new OsxAptioFix2Drv-64.efi is not working for everyone, perhaps it should be renamed OsxAptioFix3Drv-64.efi (or some other name) and original behavior of OsxAptioFix2Drv-64.efi retained.

Not to mention undoing the changes in OsxAptioFixDrv-64.efi that prevent it from being used at all (as you implied in a previous post).

Funky frank · January 12, 2018

What about naming it then like:

OsxAptioFixDrv-1011up-64.efi
OsxAptioFixDrv-1010down-64.efi

Or similar...? I don't find the numbering 1,2,3 very useful for non-hackers.

gujiangjiang · January 12, 2018

@apianti

Tested new OsxAptioFix2Drv-64.efi on my NUC6 Skull Canyon (NUC6i7KYK) with 10.13.2.

Tested by merging in changes to my own Clover fork.

It booted no problem and was able to eliminate EmuVariableUefi-64.efi and still have working NVRAM.

Will test on other computers in the coming days.

But since the new OsxAptioFix2Drv-64.efi is not working for everyone, perhaps it should be renamed OsxAptioFix3Drv-64.efi (or some other name) and original behavior of OsxAptioFix2Drv-64.efi retained.

Not to mention undoing the changes in OsxAptioFixDrv-64.efi that prevent it from being used at all (as you implied in a previous post).

Or it can be renamed as LowMemFixup.efi because this problem is a common problem not only in ami aptio bios.

从我的 iPhone 发送，使用 Tapatalk

Slice · January 12, 2018

What about naming it then like:
OsxAptioFixDrv-1011up-64.efi
OsxAptioFixDrv-1010down-64.efi
Or similar...? I don't find the numbering 1,2,3 very useful for non-hackers.

No, these names are historical.

Fix1 is more advanced.

Fix2 is simplified but supported hibernation.

@apianti

Tested new OsxAptioFix2Drv-64.efi on my NUC6 Skull Canyon (NUC6i7KYK) with 10.13.2.

Tested by merging in changes to my own Clover fork.

It booted no problem and was able to eliminate EmuVariableUefi-64.efi and still have working NVRAM.

Will test on other computers in the coming days.

But since the new OsxAptioFix2Drv-64.efi is not working for everyone, perhaps it should be renamed OsxAptioFix3Drv-64.efi (or some other name) and original behavior of OsxAptioFix2Drv-64.efi retained.

Not to mention undoing the changes in OsxAptioFixDrv-64.efi that prevent it from being used at all (as you implied in a previous post).

I agree there must be Fix3 retaining old Fix1 and Fix2.

And see new one AptioMemoryFix

Funky frank · January 12, 2018

Hey slice,

can I add new entries to a plist, using the kext patcher in clover? I read somewhere it only can replace 1:1 lengths?

More specific: How do I replace a

      <key>UnifiedSleepSliderPref</key>
      <true/>

to

      <key>UnifiedSleepSliderPref</key>
      <false/>

Also, does it work with plugins of kexts?

Path is:

/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/Mac-27ADBB7B4CEE8E61.plist

(For iMac14,2)

el_charlie · January 12, 2018

Hey slice,

can I add new entries to a plist, using the kext patcher in clover? I read somewhere it only can replace 1:1 lengths?

More specific: How do I replace a
      <key>UnifiedSleepSliderPref</key>
      <true/>
to
      <key>UnifiedSleepSliderPref</key>
      <false/>
Also, does it work with plugins of kexts?

Path is:
/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/Mac-27ADBB7B4CEE8E61.plist
(For iMac14,2)

Only info.plists of kexts and a find/replace situation. If the above string were on a info.plist the way it could work is to select the text to replace with an Hex editor plus an aditional byte to replace a string of the same length because false is larger than true.

Funky frank · January 13, 2018

Hm, ok, I geddit: The replace is like that, because it replaces on the memory of the kext cache, so no real xml/plist logic inside, just raw search/replace...

I could remove one tab then...

3c6b6579 3e556e69 66696564 536c6565 
070536c6 96465725 07265663 c2f6b657 
093e0a20 20202020 203c7472 75652f3e

to

3c6b6579 3e556e69 66696564 536c6565
070536c6 96465725 07265663 c2f6b657
093e0a20 20202020 3c66616c 73652f3e

So in clover config:

		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>unified powercontrol off</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				PGtleT5VbmlmaWVkU2xlZQBwU2xpZGVyUHJlZjwva2UH
				CT4KICAgICAgPHRydWUvPg==
				</data>
				<key>InfoPlistPatch</key>
				<true/>
				<key>Name</key>
				<string>X86PlatformPlugin.kext</string>
				<key>Replace</key>
				<data>
				PGtleT5VbmlmaWVkU2xlZQcFNsaWRlclByZWY8L2tlcJ
				PgogICAgIDxmYWxzZS8+
				</data>
			</dict>
		</array>

But how do I address the Resource dir inside that kext? Since the sub path is:

IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources/Mac-27ADBB7B4CEE8E61.plist

How to target it? Just Name = "X86PlatformPlugin.kext"? EDIT: No, that does not work. Then "com.apple.driver.X86PlatformPlugin" ? Or the outer kext, "IOPlatformPluginFamily.kext" ?

TheRacerMaster · January 13, 2018

Hey slice,

can I add new entries to a plist, using the kext patcher in clover? I read somewhere it only can replace 1:1 lengths?

More specific: How do I replace a
      <key>UnifiedSleepSliderPref</key>
      <true/>
to
      <key>UnifiedSleepSliderPref</key>
      <false/>
Also, does it work with plugins of kexts?

Path is:
/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/Mac-27ADBB7B4CEE8E61.plist
(For iMac14,2)

CPUFriend (Lilu plugin by PMHeart) can be used for this (inject the modded plist as cf-frequency-data).

Badruzeus · January 13, 2018

@Slice,

Thanks for applied this proposition:

-!ifdef ANDX86
+#!ifdef ANDX86
   DEFINE ANDX86_FLAG = -DANDX86
-!endif
+#!endif

Have a nice day!

Slice · January 13, 2018

Hey slice,

can I add new entries to a plist, using the kext patcher in clover? I read somewhere it only can replace 1:1 lengths?

More specific: How do I replace a
      <key>UnifiedSleepSliderPref</key>
      <true/>
to
      <key>UnifiedSleepSliderPref</key>
      <false/>
Also, does it work with plugins of kexts?

Path is:
/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/Mac-27ADBB7B4CEE8E61.plist
(For iMac14,2)

I think it is possible if carefully follow the instructions

Post#48 Info.plist patching

But I am not sure if the kext is present in kernelcache. Else the patching is impossible.

Funky frank · January 13, 2018

Ok, thx. Not willing to make a dissertation about clover config though. No idea, so I am changing the plist now directly.

chris1111 · January 13, 2018

Correct me if I am wrong but OsxFatBinaryDrv-64.efi was a Mandatory Drivers not visible since very short time

and now visible and selectable. This has never and to mention and why? No description about the Drivers in the Packages ?

Sorry for my ignorance

Thanks

mhaeuser · January 13, 2018

Correct me if I am wrong but OsxFatBinaryDrv-64.efi was a Mandatory Drivers not visible since very short time

and now visible and selectable. This has never and to mention and why? No description about the Drivers in the Packages ?

Sorry for my ignorance

Thanks

It's not needed since... Idk, Mavericks?

chris1111 · January 13, 2018

It's not needed since... Idk, Mavericks?

This Driveras was mandatory and was installed in the Package for years

Did you used Clover Package or not

mhaeuser · January 13, 2018

This Driveras was mandatory and was installed in the Package for years

Did you used Clover Package or not

So what? It is not needed for any macOS since 10.9, how does what I use matter?

Mr MagOO · January 13, 2018

Hello,

I'm actually trying to use the "slots" option in SMbios config .

I use this in config plist :

			<dict>
				<key>Device</key>
				<string>Firewire</string>
				<key>ID</key>
				<integer>5</integer>
				<key>Name</key>
				<string>Firewire Port</string>
				<key>Type</key>
				<integer>1</integer>
			</dict>

with "Name (_SUN, 0x05)" in DST.

It give me a "HDMI port" in slot name instead of "Firewire port".

Am I doing something wrong ?

PS : Nvidia, LAN and WIFI SMbios slots are working well...

Edit : works with SUN = 6, nothing for SUN = 5 in DSDT but my Nvidia GFX creates it automatically

vit9696 · January 13, 2018

I say we try something different, protect reserved regions differently. Because macOS does not make a difference between runtime and non-runtime reserved, it only maps the runtime reserved as the same as runtime data. But I would have to think that there is a reason those reserved regions exist and according to the spec you are not supposed to use the memory regardless of the runtime flag. So maybe we should try protected runtime reserved as runtime code and non runtime reserved as runtime data?

vit, that's only half the range when slide >= 128 for non SB and IB. What about 0x200000 to 0xFE00000? Also, this is a bad idea what if that's where the runtime was just protected? Don't want to wipe that.

EDIT: Oops left part of sentence out, lol.

I suppose you miscalculated some stuff. I did implement memory reservation code for IGPU, but the only thing it brought were more frequent boot failures from what I can tell.

You may play with it by setting APTIOFIX_PROTECT_IGPU_SANDY_IVY_RESERVED_MEMORY to 1.

WinstonAce · January 13, 2018

Correct me if I am wrong but OsxFatBinaryDrv-64.efi was a Mandatory Drivers not visible since very short time

and now visible and selectable. This has never and to mention and why? No description about the Drivers in the Packages ?

Sorry for my ignorance

Thanks

This are the mandatory drivers (without FV support)

Slice · January 13, 2018

Correct me if I am wrong but OsxFatBinaryDrv-64.efi was a Mandatory Drivers not visible since very short time

and now visible and selectable. This has never and to mention and why? No description about the Drivers in the Packages ?

Sorry for my ignorance

Thanks

It is not a mandatory driver since 10.9.

It is the driver to support FAT Binary Boot.efi. The last one was 10.8.1 AFAIK.

Since 10.9 boot.efi is just 64bit driver.

chris1111 · January 13, 2018

It is not a mandatory driver since 10.9.

It is the driver to support FAT Binary Boot.efi. The last one was 10.8.1 AFAIK.

Since 10.9 boot.efi is just 64bit driver.

This Divers is not Visible in Your today latest available source Forge Packages ➤ R4369 since for Years

and is installed By Default Mandatory for about 5 years

This Drivers is Installed if you choose UEFI Install

------------------------------------------------------------------------------------

EDIT ***

And now with the latest commit I compile the source and create the Package and now Today the Drivers is not Mandatory

Is selectable in the Package.

This is my question Why for long time is a mandatory Drivers installed by Default and Today its not mandatory ?

Slice · January 14, 2018

Some "bugs" live long time. We had to make this driver to be not mandatory since 5 years ago.

interferenc · January 14, 2018

Hey,

I am trying to find our why I need VoodooTSCSycn on my x299 system.

I am comparing my published efi platform data to one from a a real iMacPro. The obvious differences are (other keys are removed for clarity):

iMacPro

| +-o platform <class IOService, id 0x100000113, !registered, !matched, active, busy 0, retain 7>

| {

| "board-rev" = <09>

| "InitialTSC" = <26486eee7a2a0000>

| "apple-coprocessor-version" = <00000200>

| "FSBFrequency" = <00105e5f00000000>

| "board-id" = <"Mac-7BA5B2D9E42DDD94">

| }

My x299 hack

| +-o platform <class IOService, id 0x100000113, !registered, !matched, active, busy 0, retain 9>

| {

| "CPUFrequency" = <40e6a2d600000000>

| "FSBFrequency" = <6717f60500000000>

| "InitialTSC" = <984a9bd600000000>

| }

So iMacPro has a board-rev and board-id property, but I don't think that matters here.

More interestingly, there is no CPUFrequency on the real mac, and that key is not referenced anywhere in the kernel or boot.efi. So while this is a difference, it probably does not matter (i can boot without one).

The FSBFrequency on the iMacPro is 1600Mhz, like if it was multiplied by the logical core count(16*100Mhz). In the kernel, FSBFrquency is not used for skylake cpu family, but there is a reference in boot.efi, so it might matter.

And the most interesting, the InitialTSC value is 3600501400Hz for my system, and that is probably correct. However, this field on the iMacPro looks like it should not contain the TSC frequency, but the intital tsc tick value, something like you can read by rdtsc64(). This value is read by the kernel to tsc_at_boot and then used like this in one point:

if (tsc_rebase_abs_time == 0) tsc_rebase_abs_time = _rtc_tsc_to_nanoseconds(rdtsc64() - tsc_at_boot, rntp);

Which makes it clear that this value should indeed be a tick number, not a frequency value.

At another point, tsc_at_boot is stored in sysctl like this:

SYSCTL_QUAD(_machdep_tsc, OID_AUTO, at_boot, CTLFLAG_RD|CTLFLAG_LOCKED, &tsc_at_boot, "");

That variable on my system after boot is:

machdep.tsc.at_boot: 0

Which is interesting, as it is set on efi/platform, but somehow ends up being 0.

So my questions are:

Why is the FSBFrequency 1600Mhz on the iMacPro? Does it even matter?
Is the InitialTSC value calculated by clover properly? The use of this value by the kernel indicates it is not.

chris1111 · January 14, 2018

Some "bugs" live long time. We had to make this driver to be not mandatory since 5 years ago.

ok thanks Slice , understand me well I was just surprised to see him appear in the list of UEFI Drivers in my last compilation.

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