Jump to content

Clover General discussion

Bootloader EFI Clover

  • Please log in to reply
16427 replies to this topic

#16321
TheRacerMaster

TheRacerMaster

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 850 posts
  • Gender:Male

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).



#16322
Badruzeus

Badruzeus

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 660 posts
  • Gender:Male
  • Location:Indonesia
  • Interests:Graphics Design.

@Slice,

Thanks for applied this proposition:

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

Have a nice day!  :)



#16323
Slice

Slice

    InsanelyMac V.I.P.

  • Local Moderators
  • 6,761 posts
  • Gender:Male
  • Location:Moscow

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.



#16324
Funky frank

Funky frank

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 570 posts

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



#16325
chris1111

chris1111

    Packager

  • Donators
  • 4,596 posts
  • Gender:Male
  • Location:Montreal Canada
  • Interests:Mac OS X Packaging / scripts

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

 

Attached Files



#16326
Download-Fritz

Download-Fritz

    ygolohcysp desreveR

  • Developers
  • 883 posts
  • Gender:Not Telling

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?

#16327
chris1111

chris1111

    Packager

  • Donators
  • 4,596 posts
  • Gender:Male
  • Location:Montreal Canada
  • Interests:Mac OS X Packaging / scripts

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



#16328
Download-Fritz

Download-Fritz

    ygolohcysp desreveR

  • Developers
  • 883 posts
  • Gender:Not Telling

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?

#16329
Mr MagOO

Mr MagOO

    InsanelyMac Protégé

  • Members
  • PipPip
  • 53 posts
  • Gender:Male

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



#16330
vit9696

vit9696

    InsanelyMac Sage

  • Developers
  • 298 posts
  • Gender:Male

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.



#16331
WinstonAce

WinstonAce

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 655 posts

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)

Attached Files



#16332
Slice

Slice

    InsanelyMac V.I.P.

  • Local Moderators
  • 6,761 posts
  • Gender:Male
  • Location:Moscow

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.



#16333
chris1111

chris1111

    Packager

  • Donators
  • 4,596 posts
  • Gender:Male
  • Location:Montreal Canada
  • Interests:Mac OS X Packaging / scripts

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

 

Spoiler

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

 

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 ?

 

Spoiler

 

 

 

 



#16334
Slice

Slice

    InsanelyMac V.I.P.

  • Local Moderators
  • 6,761 posts
  • Gender:Male
  • Location:Moscow

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



#16335
interferenc

interferenc

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts

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.


#16336
chris1111

chris1111

    Packager

  • Donators
  • 4,596 posts
  • Gender:Male
  • Location:Montreal Canada
  • Interests:Mac OS X Packaging / scripts

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.



#16337
cecekpawon

cecekpawon

    InsanelyMac Legend

  • Developers
  • 944 posts
  • Gender:Male

Fastest way to include the new AptioFix into edk2 dir to work with Clover / other projects:

cd edk2
svn checkout https://github.com/vit9696/AptioFix/trunk/AptioFixPkg
#update
svn up

Include to dsc:

[Components]
  ...
  AptioFixPkg/Platform/AptioInputFix/AptioInputFix.inf
  AptioFixPkg/Platform/AptioMemoryFix/AptioMemoryFix.inf

* AptioMemoryFix need BaseRngLib
* AptioInputFix need some of external CupertinoNet libs

 

EDIT1: Or just call build AptioFixPkg.dsc from e/cbuild script LOL

EDIT2: More easier now

git clone https://github.com/vit9696/AptioFixPkg

Edited by cecekpawon, 14 January 2018 - 03:49 PM.


#16338
nms

nms

    InsanelyMac Protégé

  • Coders
  • 28 posts
  • Gender:Not Telling

Fastest way to include the new AptioFix into edk2 dir to work with Clover / other projects:

cd edk2
svn checkout https://github.com/vit9696/AptioFix/trunk/AptioFixPkg
#update
svn up

Include to dsc:

[Components]
  ...
  AptioFixPkg/Platform/AptioInputFix/AptioInputFix.inf
  AptioFixPkg/Platform/AptioMemoryFix/AptioMemoryFix.inf

EDIT: Or just call build AptioFixPkg.dsc from e/cbuild script LOL

 

* AptioMemoryFix need BaseRngLib
* AptioInputFix need some of external CupertinoNet libs

No need to stuff vit9696 packages to edk2/ or clover/. It can be anywhere -- environment variable PACKAGES_PATH invented exactly for that. See edk2 docs.



#16339
gujiangjiang

gujiangjiang

    An Orthopedic Graduate Student In Medical University.

  • Members
  • PipPipPipPipPip
  • 293 posts
  • Gender:Male
  • Location:Changzhou,China
More problem.

I just saw vit9696 have update his AptioMemFix and add IGPU mem fix.

I think this maybe good for HD3000 who face glitches.

But I use LegacyClover with HD3000 also have glitches. How can I do?

Can I add AptioMemFix to Drivers64 with LegacyClover?


从我的 iPhone 发送,使用 Tapatalk

#16340
cecekpawon

cecekpawon

    InsanelyMac Legend

  • Developers
  • 944 posts
  • Gender:Male

No need to stuff vit9696 packages to edk2/ or clover/. It can be anywhere -- environment variable PACKAGES_PATH invented exactly for that. See edk2 docs.

 

Poor me, DF told me about Multiple_Workspace while ago and Im not following his suggest until you link me to the right doc. Thanks nms! And you DF!







Also tagged with one or more of these keywords: Bootloader, EFI, Clover


8 user(s) are reading this topic

2 members, 6 guests, 0 anonymous users


© 2017 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy