Bootloader Chameleon 2.4svn Official PKG Installer

[Micky1979]

Replaced the boot file on my EFI and OS X won't boot now. Stuck loading the graphics (IOBluetooth Error). My GT 430 just needs GE=Yes no web drivers needed. 

 

Edit: Fixed by replacing the boot file using Windows with r2848

Sorry but this is not a fix. Try to type NoFileNVRAM at boot. Modded kernels for AMD like your may be incompatible.

Please, I need help with web driver Nvidia: MacOs does not load driver nvidia.

Must I select some setting (nv_disable=1 not work for me)?

 

in the download page http://www.insanelymac.com/forum/files/file/71-enoch/I read

 

• - Ability to load Nvidia Webdriver (Sierra) (by Micky1979)

Enoch 2848 require nvda_drv=1 under Kernel Flags. You can type this at boot time. Off course web drivers must be compatible with your card.

 

 

May be a problem of FileNVRAM? http://www.insanelymac.com/forum/topic/231075-chameleon-23svn-official-pkg-installer-binaries/page-194?do=findComment&comment=2283157

or is a problem of version? I have installed the 10.12.1.

 

Do I need to run something post OS installation (for fakesmc ad example) or Enoch has all we need?

 

But you did not read at least this page, just five posts above?

[gabryele]

http://www.insanelymac.com/forum/topic/231075-chameleon-23svn-official-pkg-installer-binaries/page-204?p=2376053&do=findComment&comment=2376053

 

I'm confused and not too good in english

 

 

 

Off course web drivers must be compatible with your card.

 

If the Nvidia driver works with clover, I think of yes. (I have MSI GTX 980)

 

I used the same settings of El Capitan (where it works)

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>EnableHDMIAudio</key>

<string>Yes</string>

<key>Graphics Mode</key>

<string>1920x1080x32</string>

<key>HDAEnabler</key>

<string>Yes</string>

<key>Kernel Flags</key>

<string>kext-dev-mode=1 nvda_drv=1</string>

<key>SMBIOS</key>

<string>/SMBios.plist</string>

<key>Timeout</key>

<string>4</string>

<key>UseKernelCache</key>

<string>Yes</string>

</dict>

</plist>

 

 

but don't understand why it does not work (from this morning I don't get anything)

 

HELP me Please

 

if I put Graphicsenabler on NO I have:

 

 

if I put Grapghicsenabler on YES I have:

 

 

but driver not loaded

 

If I reinstall a clean MacOS system, can you tell me every things I have to install from the beginning (OS X first run) to the web driver?

[Micky1979]

Hi gabryele, for me is simple: you prelinkedkernel is not up to date and does not contains the Web drivers.

Read here:            #3981              and do the same steps.

[Shaneee]

Sorry but this is not a fix. Try to type NoFileNVRAM at boot. Modded kernels for AMD like your may be incompatible.

 

Sorry I meant fix as I got back into the System. I've installed the new boot file on a USB to test and NoFileNVRAM didn't help. Either the bluetooth error or No Signal on the display. My system is using the prelinkedkernel which is working if that helps. I'll get some other AMD users to test and report then I'll let you know.

[jsl]

Ok boot file attached.

 

kexts patcher

As I said the kext patcher can now patch prelinked kexts by adding the kext name you are intrested in to kexts.plist. Since last tests I modified the kexts.plist structure and now you have to put your custom patches under "KextsPatches":

kexts1.pngkexts2.png

 

kernel patches

As for kexts you can patch the kernel in kernel.plist under "KernelPatches":

kernel.png

 

Remind you that MatchOS, MatchBuild and Comment are optional keys.

 

NVRAM

Embedded in the boot file, there is a modified version of FileNVRAM.kext, no module. To dump the nvram you have to use NVRAM Dumper Pro.app v1.3+ (attached):

ndp.pngndp2.png

(making this app to be used in Clover the idea to add back the nvram support in Enoch   )

Embedded kext is 64bit only and I have a fork of meklort's github repository where I'll add changes soon and make a pull request to Him. So please report back.

(I'm testing it also with real nvram in Clover.. and apparently works well, plus the driver add some missing stuff ,  but for that I've to check more)

 

Note

Olds FileNVRAM.dylib and KernelPatcher.dylib prevent the internal kernel patcher to do their things but still allow the kexts patcher.

FileNVRAM.dylib if loaded cause the internal nvram stuff in a off state.

Why? Just avoiding conflicts, so you can decide to use one or another, but for this tests mentioned modules shoud be removed.

FileNVRAM.kext if already present in Extra/Extensions, /S/L/E or /L/E should be removed.The one from the bootloader should win against it. Delete it anyway.

 

Now you can use the NVDIA Web Drivers by adding the relative arg when pressing the relative option in the NVIDIA Web Drivers Manager, or add it manually. Old patch I made is unnecessary and deprecated, deleted!

 

kernel.plist and kexts.plist attached as example to follow. Other old option are still there.

 

Please report back!

Thanks for this new boot file which worked perfectly for AMD FX-6300 hackintosh at 10.12.3

But for Z87 hackintosh it can not load NvidiaWebDriver at 10.12.x even booted with nvda_drv=1

Previous Enoch r.2848 can load it properly with the same prelinkedkernel.

So besides boot argument "nvda_drv=1" in org.chameleon.Boot.plist in /Extra

is there any other nvram.plist or kext.plist should be in /Extra ?

[gabryele]

Hi gabryele, for me is simple: you prelinkedkernel is not up to date and does not contains the Web drivers.

Read here:            #3981              and do the same steps.

 

only that?

 

 

please use this command line:  InsanelyRepairPermission.zip   31.68KB   8 downloads

sudo InsanelyRepairPermission -r /

then run this, and please post the log from the Terminal:

sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo kextcache -system-prelinked-kernel

[gabryele]

I have this error:

 

 

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

Error: -r is not a valid Volume!

Usage:

to verify:

sudo InsanelyRepairPermission -v /Volumes/Your Volume

 

to repair:

sudo InsanelyRepairPermission -r /Volumes/Your Volume

 

to repair and touch (will cause the kernelcache/prelinked to be rebuilt):

sudo InsanelyRepairPermission -rt /Volumes/Your Volume

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

 

 

where can I put the InsanelyRepairPermission.zip? it's on desktop now.

 

I try also with sudo /Users/nomeutente/Desktop/InsanelyRepairPermission -r /Volumes/Mac HD

but NOTHING   

 

this is my hd list

 

 

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.1 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                  Apple_HFS Mac HD                  499.2 GB   disk0s2

   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

 

 

with this command sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo kextcache -system-prelinked-kernel I have:

 

 

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_LPCSensors.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_GPUSensors.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_CPUSensors.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext

KernelCache ID: 7472C39709D4C4C6D2588CB645A39310

[mitch_de]

The problem is the space in the Volume name! (alwaysw a problem if you type the name in).

/Volumes/Mac HD  ......  means a space!

Hint: dont type the Volume name or any other path/App name with spaces in!

Use  drag & drop  to put the rigth volume name into the terminal.

1. type sudo /Users/nomeutente/Desktop/InsanelyRepairPermission -r 

2. drag & drop the volume into the terminal (be sure you have one space  after -r)

3. press enter

 

PS: you can also drag& drop the app/tool same way,

open terminal.   means a space

sudo Drag&drop_the_app_or_tool -r Drag&drop_the_volume

With this you avoid space problems in any path/name and! also much less typing.

 

Happy drag&dropping

[gabryele]

I don't know HOW, but NOW works...

I change only org.chameleon.Boot.plist

 

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Graphics Mode</key>

<string>1920x1080x32</string>

<key>Kernel Flags</key>

<string>kext-dev-mode=1 nvda_drv=1</string>

<key>KeyLayout</key>

<string>mac-it</string>

<key>SMBIOS</key>

<string>/SMBios.plist</string>

<key>Timeout</key>

<string>4</string>

<key>UseIntelHDMI</key>

<string>Yes</string>

<key>UseKernelCache</key>

<string>Yes</string>

</dict>

</plist>

 

and kernel.plist

 

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>KernelBooter_kexts</key>

<string>Yes</string>

</dict>

</plist>

 

 

but, there is a BUT

In the Nvidia icon I see select OS X default graphics driver...

why?

is a fake information?

 

 

[mitch_de]

Yep, the Nvidia Menue Information is wrong - but only an cosmetic problem. I think that checks Nvidia/OS X drivers used by nvram check, which fails using the chameleon patching NV use way.

So, we could disable ".. show in Menue Bar" option of the Nvidia Prefpane because its wrong.

 

My WebdriverCheck (in download sektionof the forum) tool shows the real life  - if you see com.nivida....Web  then you use the web drivers and not OS X default drivers.

[Micky1979]

Hi guys, I'm working to fix the nvram that in my second pc is not good. Later I'll hope that web drivers will work that way only..

[gabryele]

Hi guys, I'm working to fix the nvram that in my second pc is not good. Later I'll hope that web drivers will work that way only..

 

I'm ready to test it

 

 

the boot r2851 nvram+kextsPatcher.zip does not work for me 

[PippoX0]

Ok boot file attached.

 

kexts patcher

As I said the kext patcher can now patch prelinked kexts by adding the kext name you are intrested in to kexts.plist. Since last tests I modified the kexts.plist structure and now you have to put your custom patches under "KextsPatches":

kexts1.pngkexts2.png

 

kernel patches

As for kexts you can patch the kernel in kernel.plist under "KernelPatches":

kernel.png

 

Remind you that MatchOS, MatchBuild and Comment are optional keys.

 

NVRAM

Embedded in the boot file, there is a modified version of FileNVRAM.kext, no module. To dump the nvram you have to use NVRAM Dumper Pro.app v1.3+ (attached):

ndp.pngndp2.png

(making this app to be used in Clover the idea to add back the nvram support in Enoch )

Embedded kext is 64bit only and I have a fork of meklort's github repository where I'll add changes soon and make a pull request to Him. So please report back.

(I'm testing it also with real nvram in Clover.. and apparently works well, plus the driver add some missing stuff , but for that I've to check more)

 

Note

Olds FileNVRAM.dylib and KernelPatcher.dylib prevent the internal kernel patcher to do their things but still allow the kexts patcher.

FileNVRAM.dylib if loaded cause the internal nvram stuff in a off state.

Why? Just avoiding conflicts, so you can decide to use one or another, but for this tests mentioned modules shoud be removed.

FileNVRAM.kext if already present in Extra/Extensions, /S/L/E or /L/E should be removed.The one from the bootloader should win against it. Delete it anyway.

 

Now you can use the NVDIA Web Drivers by adding the relative arg when pressing the relative option in the NVIDIA Web Drivers Manager, or add it manually. Old patch I made is unnecessary and deprecated, deleted!

 

kernel.plist and kexts.plist attached as example to follow. Other old option are still there.

 

Please report back!

Very good job Micky1979 !!

 

sent from my iPhone

[jsl]

Yep, the Nvidia Menue Information is wrong - but only an cosmetic problem. I think that checks Nvidia/OS X drivers used by nvram check, which fails using the chameleon patching NV use way.

So, we could disable ".. show in Menue Bar" option of the Nvidia Prefpane because its wrong.

 

My WebdriverCheck (in download sektionof the forum) tool shows the real life  - if you see com.nivida....Web  then you use the web drivers and not OS X default drivers.

Thanks for your WebdriverCheck app.

However it crashed on open in my Z87 hackintosh.

How to fix it ?

[mitch_de]

We can discuss your crash of my WebDriverCheck tool by pm. I send you one. Thanks for report.

EDIT: "The member jsl cannot receive any new messages" Is your message box perhaps full?

[jsl]

We can discuss your crash of my WebDriverCheck tool by pm. I send you one. Thanks for report.

EDIT: "The member jsl cannot receive any new messages" Is your message box perhaps full?

I have sent a PM to you and thanks for your kind help.

Also deleted some messages and it's not full now !

The crash_report and screen are attached here:

crash_report.zip

[mitch_de]

Yep, i told him to communicate about the prob with the app using PM further , perhaps he didn't realize that- sorry.

[Micky1979]

Can I have your /System/Library/PrelinkedKernels/prelinkedkernel?

[Micky1979]

Got it thanks. I'll look into it tomorrow when I hope to have the time.

[Gigamaxx]

I picked up a Ryzen 7 1700 and Asus Prime X370 mobo. Using clover bootloader UEFI gives black screen, nothing at all appears. Using clover Legacy bootloader (attached via USB port SSD adapter ) gives me the error on bottom of post.

 

Using Enoch on USB connection gives me this.

 

 

So far with this Ryzen setup UEFI leads to black screen and legacy clover or chameleonenoch leads to at least to some error message. Is there anything I can provide to help make a bootloader that will get us into Sierra using the new Ryzen CPUs? It seems as though the Other OS option on the motherboard doesn't have an Other capability. Is there a way to collect CPU info for a bootloader upgrade/modification in windows? I was referred to this thread to check in and see if anyone has any thoughts or recommendations to help with Ryzen support. So far it seems like UEFI booting doesn't look promising.

 

[Micky1979]

@Gigamaxx, you know that you are talking about an AMD cpu? Sorry but here you need a developer that already own such that processor and that know what to do and which provide code..

And boot0:error  just  means that Enoch is bad installed, maybe you can have better results formatting your pen drive in Fat32.

[Micky1979]

Here it is:

https://mega.nz/#!ZMt3HYIa!PPOLKWBYrkkTK4lvEsR6CinOjGnZRO8bSqXuoygV3_A

 

(may fail to download with Safari, Ok with Chrome).

 

Hi Hervè, I've corrected a miscalculation, please try and report, should work now. Also if you can, test the news below  .

PS anyway to disable the kexts patcher you can type "SkipKextPatcher=Yes" (something similar also for the kernel patcher: just "SkipKP=No")

 

for all

Enoch rc1 and FileNVRAM.dylib rc1

 

Enoch rc1 has the ability to patch kernel and kexts (prelinked or not) like in the previous test versions made available some days ago in this Topic.

I've removed the internal nvram support because I worked with meklort to fix some little bugs in the old code (continue reading below).

News:

now Enoch know if you load the FakeSMC.kext or not. So what?

Well, if not found on the filesystem or not prelinked now Enoch load its embedded version automatically.

If you glad or you want make tests for me (please), you can remove it and see it loaded by Enoch.  Please report back, Ermac and I would release that code.

 

FileNVRAM.dylib module attached is a develop version of my fork (unpushed). As I said I worked with meklort to fix it, but this is radically changed and I need feedback to make a new pull request to the mantainer (meklort). So as always the module goes in Extra/module/ of the boot partition. 

PS this module dump the nvram in /.nvram.plist (hidden), but if you have the old one in /Extra/ will read this for the first time (..and w/o apporting changes to it). Later the new file location will be always on the root.

(you don't need NVRAM Dumper Pro.app to dump the nvram, and if active you should keep of it)

 

Please report back.

 

 

EDIT

new files here:             #4125            

 

Edited March 22, 2017 by Micky1979
boot file and module removed

[Micky1979]

Hi Micky, did a quick test on my E6220 Yosemite partition with no relinked kernel/cache rebuilt and I still got the same memory allocation error as before. I could only boot Yosemite with -f -v KernelBooter_kexts=Yes.

 

Booting the previously bootable Sierra partition also ended up in pseudo KP with numerous ACPI errors before a final "System uptime" message.

Thanks. Can I take a look on that kp?

[Shaneee]

Sorry but here you need a developer that already own such that processor and that know what to do and which provide code..

 

 

Is there any information someone with Ryzen can share that would help out or does a dev need one to test on?

[Micky1979]

Forget it, it was Ok on 2nd Sierra reboot.

 

So really, the issue remains as before in the Yosemite partition which was Ok again once I reverted to boot file of r2848.

Does the same with "SkipKextPatcher=Yes" at command line or in o.c.b.p?

EDIT

Did you have the kexts.plist?

Is there any information someone with Ryzen can share that would help out or does a dev need one to test on?

CPU-Z or AIDA from windows?