Jump to content

Chameleon 2.4svn Official PKG Installer


ErmaC
4,344 posts in this topic

Recommended Posts

OK, did 1,2,3 now FileNVRAM RC 3.

Worked.

Q: i deleted the .nvram.plist in / (of any partition, HD) but not the "found nvram.00000000-0000-0000-0000-001d7dd11bf3.plist at /Volumes/OSX_BACKUP/Extra [hd(2,3)]"

which got later loaded loading hd(1,2)/Extra/nvram.00000000-0000-0000-0000-001d7dd11bf3.plist: success.

Should i delete them also or was enough to delete that .nvram.plist in the root?

 

Was deleted and got new after the  install RC 3 & reboot.

 

EDIT: Now tested patch AppleRTC  = YES and OrangeIconFix  = YES

Worked! :)

[ KEXTS PATCHER START ]

Patching AppleRTC: 0 substitutions made!

Patching AppleAHCIPort: 3 substitutions made!

Kexts patcher: end!

RTC Patch has nothing to patch because i use an already patched kext.
OrangeIconFix working, orange Icons (removalble disk) gone, now grey as they should
  • Like 1
Link to comment
Share on other sites

 

OK, did 1,2,3 now FileNVRAM RC 3.

Worked.

Q: i deleted the .nvram.plist in / (of any partition, HD) but not the "found nvram.00000000-0000-0000-0000-001d7dd11bf3.plist at /Volumes/OSX_BACKUP/Extra [hd(2,3)]"

which got later loaded loading hd(1,2)/Extra/nvram.00000000-0000-0000-0000-001d7dd11bf3.plist: success.

Should i delete them also or was enough to delete that .nvram.plist in the root?

leave it as backup  :wink_anim:, the module will read it again only if no one /.nvram.plist will be found, also this ensure compatibility with the old module.

 

 Now tested patch AppleRTC  = YES and OrangeIconFix  = YES

Worked!  :)

[ KEXTS PATCHER START ]

Patching AppleRTC: 0 substitutions made!

Patching AppleAHCIPort: 3 substitutions made!

Kexts patcher: end!

RTC Patch has nothing to patch because i use an already patched kext.
OrangeIconFix working, orange Icons (removalble disk) gone, now grey as they should

 

good!

 

But the Q. now is: can you activate the NVIDIA web drivers in Sierra using only its manager?

Link to comment
Share on other sites

I will try that, last tests always El Capitan  ( my working OS X). I have Sierra 12.3 and will try that.

 

What i want to say is, that along the tests (deleting .nvram.plist, delete the dlib, ...) step 1,2,3 i get always Web driver enabled. Never had Apple default. I never have to use the Nvida Menü selection.

 

Can it be that thats because i did 1,2,3 rigth but never deleted also that /Extra/nvram.00000000-0000-0000-0000-001d7dd11bf3.plist ?

Link to comment
Share on other sites

In El Capitan there is no need for the nvram support, if you have nvda_drv=1 in the Kernel Flags it's enough (or if you have it in boot-args that it's the same exactly).  In Sierra nvram is required but here is no longer a kernel flag/boot-arg. Is a key/value pair like in a plist:

post-674334-0-81987900-1490309280_thumb.png

Link to comment
Share on other sites

Ok found my own mistake. To enable the trim patch the code looks for a matching kext name and if the variable boolean "TrimEnablerSata" is set to true then the patch get activated:

if ((!strcmp(execPath, "IOAHCIBlockStorage")) && TrimEnablerSata)

 

but was by mistake :

 

if ((!strcmp(execPath, "IOAHCIBlockStorage")) && kTrimEnablerSata)

 

kTrimEnablerSata is the name of the key in kernel.plist and is a string instead of a bool variable.

i.e never was false, fixed. (sorry but both look like the same and difficult to see)

Thanks a lot !

This boot rc5 & FileNVRAM.dylib rc3 can load NvidiaWebDriver correctly now at 10.12.3 & 10.12.4.

post-70188-0-11233800-1490321739_thumb.png

  • Like 1
Link to comment
Share on other sites

Good!

Thanks @jsl and @mitch_de for testing! I think all is fixed. Now I have to present to meklort the new code for the FileNVRAM module, hoping that He will accept the changes made.


Well, my lappy boot macOS without installing any kexts! (I have removed the FakeSMC.kext) and my Wifi is working using the "PersonalitiesInjector" in kexts.plist and No one kext is patched on the filesystem, iMessage is working as well for the Web Drivers.... I would say very good! :)

Waiting ErmaC to commit latest changes!

  • Like 2
Link to comment
Share on other sites

Yes, delete  FileNVRAM.kext and rebuild the cache.

Use the boot file attached.

Do that in a usb stick and don't forget to set KernelBooter_kexts=Yes in kernel.plist

 

ok, I put kernel.plist in extra only with KernelBooter

 

 

<dict>

    <key>KernelBooter_kexts</key>

    <string>Yes</string>

</dict>

 

then I try both boot_rc3 and boot_rc5: they work good, nvidia driver everytime selected:

 

0t2Ex2w.png

 

Senza_titolo.jpg

  • Like 1
Link to comment
Share on other sites

ok, I put kernel.plist in extra only with KernelBooter

 

 

then I try both boot_rc3 and boot_rc5: they work good, nvidia driver everytime selected:

 

0t2Ex2w.png

 

 

Yeah! thanks for testing!

Work in progress ;)

 

ErmaC

:)

Link to comment
Share on other sites

Hi! I have an AMD FX 8350 with a GTX 970.

 

I am glad to inform that nvidia webdriver loads perfectly with boot rc5 and filenvram rc 3 using the NVIDIAWebDrv=Yes bootflag.

 

I dont know if it is related but my About Mac Is not working.

 

 

Thank you for your hard work!

  • Like 1
Link to comment
Share on other sites

Hi! I have an AMD FX 8350 with a GTX 970.

 

I am glad to inform that nvidia webdriver loads perfectly with boot rc5 and filenvram rc 3 using the NVIDIAWebDrv=Yes bootflag.

 

Thank you for your hard work!

 

Thanks to you reporting this!  :thumbsup_anim:

 

I dont know if it is related but my About Mac Is not working.

Can't be (no reason other than due to your modded kernel)

Link to comment
Share on other sites

Guys, another step (boot rc6). FileNVRAM.dylib rc6 is only compatible with this rc6 or 2848 and older since I have reverted a change introduced with rc1~rc5. That is to restore compatibility, but don't use the module with previous rc files.

 

NEW:

Extra/Extensions/Common and Extra/Extensions/10.x

10.x stand for 10.4 or 10.6 ...or 10.11 or 10.12 and so on

 

If Extra/Extensions/Common is found on the bootloader-boot partition now Enoch switch to load kexts only from the boot partition. If not found it behaves as always, i.e. loads from /Extra/Extensions/ of the boot partition or override to  the /Extra/Extensions/ of the osx partition actually selected.

 

In Extra/Extensions/Common you should put inside only kexts that are compatible and loads all the OSes you have. FakeSMC.kext and plugins may stay there for example.

In Extra/Extensions/10.7 you should place only kexts compatible with Lion, in Extra/Extensions/10.12 instead you should place only kexts compatible with Sierra.

 

Warning: if /Common folder is in use, no kexts will be loaded outside /Common or /10.x

 

The goal: have only one Extra folder to dynamically load different configurations for different OSes

 

Tests appreciated since ErmaC is doing commits to update it, thanks!

boot_rc6.zip

FileNVRAM.dylib_rc6.zip

  • Like 7
Link to comment
Share on other sites

revision 2874 is up on the svn

 

All the changes, improvements update and ports made by Micky1979 are committed...

(I will w8 to publish a pre-packed pkg... the latest Micky's rc6 is the same as 2874)

 

now is time for deep testing and fixing bugs, then we can merge it to the main trunk..

 

NOTE: also for AMD developer can take this as base for his test and adding code for new cpus

 

ErmaC

  • Like 3
Link to comment
Share on other sites

In addiction the FileNVRAM.dylib on the repository is the old one, so for now use this at this post:#4153, waiting me to have time for a official pull request.

Both rc6 of boot & FileNVRAM.dylib work perfectly at 10.12.3 and 10.12.4 for my Z87 hackintosh.

Thanks again !

  • Like 1
Link to comment
Share on other sites

revision 2874 is up on the svn

 

All the changes, improvements update and ports made by Micky1979 are committed...

(I will w8 to publish a pre-packed pkg... the latest Micky's rc6 is the same as 2874)

 

now is time for deep testing and fixing bugs, then we can merge it to the main trunk..

 

NOTE: also for AMD developer can take this as base for his test and adding code for new cpus

 

ErmaC

 

Will the new pkg include the options for using kexts.plist and kernel.plist with some default values?

Link to comment
Share on other sites

Will the new pkg include the options for using kexts.plist and kernel.plist with some default values?

Yep the basics... as you have already see for the kernel.plist

also this is a work in progress..

001.png002.png

 

ErmaC

  • Like 2
Link to comment
Share on other sites

Guys, another step (boot rc6). FileNVRAM.dylib rc6 is only compatible with this rc6 or 2848 and older since I have reverted a change introduced with rc1~rc5. That is to restore compatibility, but don't use the module with previous rc files.

 

NEW:

Extra/Extensions/Common and Extra/Extensions/10.x

10.x stand for 10.4 or 10.6 ...or 10.11 or 10.12 and so on

 

If Extra/Extensions/Common is found on the bootloader-boot partition now Enoch switch to load kexts only from the boot partition. If not found it behaves as always, i.e. loads from /Extra/Extensions/ of the boot partition or override to  the /Extra/Extensions/ of the osx partition actually selected.

 

In Extra/Extensions/Common you should put inside only kexts that are compatible and loads all the OSes you have. FakeSMC.kext and plugins may stay there for example.

In Extra/Extensions/10.7 you should place only kexts compatible with Lion, in Extra/Extensions/10.12 instead you should place only kexts compatible with Sierra.

 

Warning: if /Common folder is in use, no kexts will be loaded outside /Common or /10.x

 

The goal: have only one Extra folder to dynamically load different configurations for different OSes

 

Tests appreciated since ErmaC is doing commits to update it, thanks!

Regards, I'm excited about all these new updates. With this new version of NVRAM, Recognize my ROM and my MLB automatic?

Link to comment
Share on other sites

Regards, I'm excited about all these new updates. With this new version of NVRAM, Recognize my ROM and my MLB automatic?

Off course no. You have to generate them by hand using the nvram command line to make it persistent.

EDIT

lately ROM and MLB must be calculated to be valid (mac address/uuid/smbios etc)

  • Like 1
Link to comment
Share on other sites

Yep, normal. Because Nvdia updates drivers mostly a day - 1,5 days  after OS X updates.

So if you update OS X early,  nvida has no new drivers.

Beside that - we can be happy that nvida supports us (real Mac Pro Users + hackintosh) even Apple doesn´t buy any nvidia gpus anymore  from them!

Link to comment
Share on other sites

×
×
  • Create New...