Jump to content
WarDoc

WhatEverGreen Support Topic

1,022 posts in this topic

Recommended Posts

Well ryzen issue is solved I will add it to the op soon

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
Advertisement

Still only DP. No 2nd display.

 

After updating lilu to 1.1.6, this is all i see in the log output now:

Also the connector-count i did not set, because its not documented. Maybe it should be 0x03,00,00,00 ? = 3 ports total?

 

To see log you need DEBUG version of Lilu and WhateverGreen. And as i told here before RX series doesn't need connector-count, connector-priority or custom connectors!

Share this post


Link to post
Share on other sites

I've got a question, too:

 

with this settings within my GFX-SSDT:

        Device (PLX1)
        {
            Name (_ADR, 0x00080000)  // _ADR: Address
            Device (GFX0)
            {
                Name (_ADR, Zero)  // _ADR: Address
                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    Store (Package (0x0C)
                        {
                            "AAPL,slot-name", 
                            Buffer (0x07)
                            {
                                "Slot-1"
                            }, 

                            "connectors", 
                            Buffer (0x78)
                            {
                                /* 0000 */  0x00, 0x04, 0x00, 0x00, 0x04, 0x03, 0x00, 0x00,
                                /* 0008 */  0x00, 0x01, 0x01, 0x01, 0x00, 0x00, 0x00, 0x00,
                                /* 0010 */  0x12, 0x04, 0x06, 0x01, 0x00, 0x00, 0x00, 0x00,
                                /* 0018 */  0x00, 0x04, 0x00, 0x00, 0x04, 0x03, 0x00, 0x00,
                                /* 0020 */  0x00, 0x01, 0x02, 0x01, 0x00, 0x00, 0x00, 0x00,
                                /* 0028 */  0x22, 0x05, 0x04, 0x03, 0x00, 0x00, 0x00, 0x00,
                                /* 0030 */  0x00, 0x08, 0x00, 0x00, 0x04, 0x02, 0x00, 0x00,
                                /* 0038 */  0x00, 0x01, 0x03, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 0040 */  0x11, 0x02, 0x01, 0x02, 0x00, 0x00, 0x00, 0x00,
                                /* 0048 */  0x00, 0x08, 0x00, 0x00, 0x04, 0x02, 0x00, 0x00,
                                /* 0050 */  0x00, 0x01, 0x04, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 0058 */  0x21, 0x03, 0x05, 0x04, 0x00, 0x00, 0x00, 0x00,
                                /* 0060 */  0x04, 0x00, 0x00, 0x00, 0x04, 0x00, 0x00, 0x00,
                                /* 0068 */  0x00, 0x01, 0x05, 0x00, 0x00, 0x00, 0x00, 0x00,
                                /* 0070 */  0x10, 0x00, 0x03, 0x06, 0x00, 0x00, 0x00, 0x00 
                            }, 

                            "CFG,CFG_USE_AGDC",        // <---- look here (changed boolean from "true" to "false")
                            Buffer (One)
                            {
                                 0x00                                           
                            }, 

                            "CFG,CFG_USE_CP2",        // <---- and here (changed boolean from "false" to "true")
                            Buffer (One)
                            {
                                 0x01                                           
                            }, 

                            "hda-gfx", 
                            Buffer (0x0A)
                            {
                                "onboard-1"
                            }, 

                            "@0,AAPL,boot-display", 
                            Buffer (Zero) {}
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }

I'll get this within IORegistryExplorer:

RX_Settings.jpg

As you may see in the screenshot, the values for the selected options got changed from "true" to "false" and vise versa (as expected) - so changing values through the right settings within SSDT works within WhatEverGreen.

But - and this is only cosmetic question - is it possible to hide the WhatEverGreen entries "CFG,CFG_xxx" - so that only their original entries are visable?

 

Oh, and once again: on my rig (see signature for used hardware) WhatEverGreen runs perfectly w/o any hitch. Thanx again to the guys, who made this possible after a long wait. You did a great job.

Share this post


Link to post
Share on other sites

I didn't see any connectors information in this log. Either log is not full or you made something wrong! First of all delete IntelGraphicsFixup and NvidiagraphicsFixup. Place DEBUG Lilu and DEBUG WhateverGreen in EFI/Clover/Kexts/Other. Turn InjectKexts=YES in config.plist. Remove Lilu and all plugins from L/E or S/L/E. Delete caches and prelinkedkernel. Rebuild them. Reboot and make log one more time!

 

And don't forget -raddbg -liludbg bootargs!!!! 

Share this post


Link to post
Share on other sites

Hello,

 

I have my MSI R9 290 running on Sierra (partially, only 1 output working). Currently, the only way I got this card working was by using 0x67b11002 as the FakeID and "InjectATI" on Clover, but this requires having the iGPU enabled and booting blindly to OS X. I'm trying to use Lilu + WhateverGreen to get my 3 monitors working, so I removed the FakeID and disabled the InjectATI option. Lilu and WhateverGreen get loaded, but the AMD Kext doesn't. If I add this device ID to the AMD Kext, the system loads to a black screen. I can SSH to the machine and see that the Kext got loaded, and WhateverGreen even detects all three outputs, but apart from that, I can't get the monitors to display anything. Any idea on how should I proceed?

 

Ps.: My card BIOS has UEFI support and CSM is disabled on the motherboard firmware.

Share this post


Link to post
Share on other sites

I didn't see any connectors information in this log. Either log is not full or you made something wrong! First of all delete IntelGraphicsFixup and NvidiagraphicsFixup. Place DEBUG Lilu and DEBUG WhateverGreen in EFI/Clover/Kexts/Other. Turn InjectKexts=YES in config.plist. Remove Lilu and all plugins from L/E or S/L/E. Delete caches and prelinkedkernel. Rebuild them. Reboot and make log one more time!

 

And don't forget -raddbg -liludbg bootargs!!!! 

 

ok, I did the following since last time:

 

* Removed Intel and Nvidia Graphics Fixup kexts from kexts/10.12

* Moved lilu and whatevergreen kexts from kexts/10.12 --> kexts/other (should not matter, anyhow I did it)

* Removed all NVIDIA* kexts from S/L/E that were of the date was installed by the Nevidia Web Drivers

* Ran 'Kext Utility.app' to rebuild caches

 

result = same as before. Here is the new log:

2017-08-14 19:59:40.993049+0100  localhost kernel[0]: (kernel) Lilu: (DEBUG) config @ boot arguments disabled 0, debug 1, slow 0, decompress 1
...
<removed>
...
2017-08-14 19:59:45.906080+0100  localhost kernel[0]: (kernel) Lilu: (DEBUG) patcher @ invoked at kext loading/unloading
2017-08-14 19:59:45.906082+0100  localhost kernel[0]: (kernel) Lilu: (DEBUG) patcher @ last kext is <private> and its name is com.apple.driver.AppleHWSensor
ga-z170x-g3:~ root# 

Many thanks. If you have some other suggestions, for example maybe to find the GPU in IORegistryExplorer? They will also provided, just have to upload them.

 

AKSENOD.png

 

Card is this one: http://www.xfxforce.com/en-us/products/amd-radeon-rx-500-series/rx-550-2gb-ss-rx-550p2tfg5

ok heres my ioreg (or io jones) files.

dreamcat4 - rx550 - ports not recognized - ioreg and iojones files.zip

Share this post


Link to post
Share on other sites

Dream cat please edit your posts to remove the log and use paste bin thanks

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

ok... it turns out nobody else seems to have done rx550 yet. --> There is no success story. In clover configurator I just set fakeid to 0x67ef1002, which is supposed to be 67ef = rx460, and 1002 = ati. So then config.plist looks like this:

		<key>FakeID</key>
		<dict>
			<key>ATI</key>
			<string>0x67ef1002</string>

Rebooted but no different. And system profiler showing same previous gpu device id... like the fakeid set inside clover did not work.

 

YV3NDpO.png

 

This is a shame. Because I assumed there was rx550 supported... ah well. :help:

Share this post


Link to post
Share on other sites

ok... it turns out nobody else seems to have done rx550 yet. --> There is no success story. In clover configurator I just set fakeid to 0x67ef1002, which is supposed to be 67ef = rx460, and 1002 = ati. So then config.plist looks like this:

 

Rebooted but no different. And system profiler showing same previous gpu device id... like the fakeid set inside clover did not work.

 

This is a shame. Because I assumed there was rx550 supported... ah well. :help:

 

Well you should know that FakeID will work ONLY if you inject ATI in config.plist or use FixDisplay. Obviously neither of this methods can't be used with WhateverGreen. So probably i should forward you to read the FAQ? But who wants to read it? Everybody here knows that the FAQ is useless :lol:

OK. One last time.

You should use device-id injection either with SSDT or with Arbitrary. SSDT method described in "useless FAQ" and Arbitrary method should be like this. Your fake device-id is already on the screenshot below

post-1069282-0-45371900-1502753621_thumb.png

 

Have fun...

 

P.S.  If you prefer copy-paste here is the code

		<key>Arbitrary</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>Inject AMD Graphics properties</string>
				<key>CustomProperties</key>
				<array>
					<dict>
						<key>Key</key>
						<string>device-id</string>
						<key>Value</key>
						<data>
						72cAAA==
						</data>
					</dict>
					<dict>
						<key>Key</key>
						<string>model</string>
						<key>Value</key>
						<string>Radeon Pro 550</string>
					</dict>
				</array>
				<key>PciAddr</key>
				<string>01:00.00</string>
			</dict>
		</array>

Share this post


Link to post
Share on other sites
ok... it turns out nobody else seems to have done rx550 yet. --> There is no success story. In clover configurator I just set fakeid to 0x67ef1002, which is supposed to be 67ef = rx460, and 1002 = ati. So then config.plist looks like this:

<key>FakeID</key>
		<dict>
			<key>ATI</key>
			<string>0x67ef1002</string>
Rebooted but no different. And system profiler showing same previous gpu device id... like the fakeid set inside clover did not work.

 

YV3NDpO.png

 If 560X worked by patch info.plist of AMD9510Controller.kext, you may change it for trial too !

From 69ef1002 to yours .

Share this post


Link to post
Share on other sites

Thanks! :thumbsup_anim:

 

Add these to your Main Partition or Drive in System/Library/Extensions folder.    Make sure to run Kext wizard before reboot.

 

Open your S/L/Extensions folder and drag copies of these two kexts (originals) to desktop as extra copies before you add the provided ones with edits.    It will ask for "Authentication" and "replace" prompts.   Don't forget Kext wizard before reboot.

RX 550 KExts for Sierra 12.6.zip

Share this post


Link to post
Share on other sites

Thanks guys, these suggestions are really appreciated despite the card being unsupported in sierra (maybe its different in high sierra, i didnt check / see yet). Please also bear in mind I can still return this rx550 card if it cannot work. Which I will likely to anyways due to unnaceptable bearing / rattling noise in the fan anyhow,

 

Add these to your Main Partition or Drive in System/Library/Extensions folder.    Make sure to run Kext wizard before reboot.

 

Open your S/L/Extensions folder and drag copies of these two kexts (originals) to desktop as extra copies before you add the provided ones with edits.    It will ask for "Authentication" and "replace" prompts.   Don't forget Kext wizard before reboot.

 

Tried this one first.... did not seem to do anything. And the device id in system profiler was still not changed.


Well you should know that FakeID will work ONLY if you inject ATI in config.plist or use FixDisplay. Obviously neither of this methods can't be used with WhateverGreen. So probably i should forward you to read the FAQ? But who wants to read it? Everybody here knows that the FAQ is useless :lol:

OK. One last time.

You should use device-id injection either with SSDT or with Arbitrary. SSDT method described in "useless FAQ" and Arbitrary method should be like this. Your fake device-id is already on the screenshot below

 

Have fun...

 

P.S.  If you prefer copy-paste here is the code

		<key>Arbitrary</key>
		<array>
			....

 

Thanks. Sorry for being such a moron about all this. I do try to read things but am one of those people who immediately looks away when they see the works 'DSDT' mentioned. Anyhow I did put back my fakeid to 0x0 in clover, and tried your 2nd suggested method 'Arbitrary'....

 

Perhaps it worked, at least I believe it worked because after reboot, near the end once its got to the point of loading GPU driver (saying 'GreenLockState...' and pausing / waiting). Well at that point its then always a hard reset. I tried also changing the 2nd byte after the 67ef to 0201 (for ati vendor id in reverse byte order).

 

If the arbitrary method you gave me has worked, but maybe for whatever reason(s) the polaris12 die is not close enough to baffin. And cannot use same baffin driver. This maybe make sense because different silicon means different number of CUs / sms / whatever. So you cannot address some of the last CUs on smaller silicon because they simply are not exist on the die.

 

Anyhow (like I said earlier)... maybe High Sierra 10.13 has a new support for polaris12 i dont know myself. Just have been avoiding trying these DP until final release is out. And as you have noticed I'm not really the smartest kid on the block to contribute with such things.

 

OK I will probably keep this card for a few days more, in case there are any other developments which need further testing. Then return the rx550 for gt1030.

Share this post


Link to post
Share on other sites

OK I will probably keep this card for a few days more, in case there are any other developments which need further testing. Then return the rx550 for gt1030.

 

Try to change in Arbitrary array EF67->FF67. And you don't need 0201 in the end of line!!! It should look like FF670000

Share this post


Link to post
Share on other sites

Try to change in Arbitrary array EF67->FF67. And you don't need 0201 in the end of line!!! It should look like FF670000

 

Sorry but its hard reset during the boot sequence again. This time there was no pause @ GreenLockState at end, but it said Lilo then rebooted immediately. So it maybe it reset a little earlier in the boot sequence. that was because i had moved kexts back. Now its same place reset.

[EDIT] actually i will try this again, because had reverted back some other preferred kexts stuff you asked me to change.

 

OK so with arbitrary FF id the reset occurs in same place. What is annoying to me is that during the verbose messages i can see the debug output working for Lilu and WhateverGreen. Yet after it resets the computer then the log command:

root# log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source

does not show up the messages. Maybe that is because the HFS+ journalling rolls back. (inconsistent FS state). Or else it just simply didn't flush to disk the log yet (it rebooted before that). Anyhow nevermind.

 

I keep looking for other forums and again... for example 2 month ago saying:

 

> There is no 699F device ID in the kexts to allow Polaris 12 work in Mac OS.

 

https://forums.macrumors.com/threads/amd-polaris-gpus-plug-and-play-in-macos-10-12-6-10-13.2050945/#post-24723518

 

Unless they added in new high sierra DPs, which is not mentioned yet in any other threads (i cannot find). And for example the device id of rx560 (0x67FF) is just still polaris 11 die, with more unlocked CUs (not less CUs) than rx460.

 

OK well like you said before - a device not supported by MacOS... is not actually a problem in GreenShot plugin. But many thanks here for trying to help! Kind Regards.

Share this post


Link to post
Share on other sites

Is there a possibility to enable graphic acceleration with

 

MB: Asus Z170 Pro Gameing

Graphiccard: MSi Radeon RX 470

 

Operating system: OS X 10.12.6

 

using lilu.kext and whatsevergreen.kext in current versions in Other-Folder of EFI/Clover ....

 

Problem:

Clover booting ends with black screen.

 

Only possibility to log in the operating system: 

In clover menu -> graphic injection -> faked 0x12345678.

But then there is no graphic acceleration

Share this post


Link to post
Share on other sites

Is there a possibility to enable graphic acceleration with

MB: Asus Z170 Pro Gameing

Graphiccard: MSi Radeon RX 470

Operating system: OS X 10.12.6

using lilu.kext and whatsevergreen.kext in current versions in Other-Folder of EFI/Clover ....

Problem:

Clover booting ends with black screen.

Only possibility to log in the operating system:

In clover menu -> graphic injection -> faked 0x12345678.

But then there is no graphic acceleration

with weg don’t use injection also turn off csrutil from recovery by typing csrutil disable then reboot and hope for the best

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

Thanks guys, these suggestions are really appreciated despite the card being unsupported in sierra (maybe its different in high sierra, i didnt check / see yet). Please also bear in mind I can still return this rx550 card if it cannot work. Which I will likely to anyways due to unnaceptable bearing / rattling noise in the fan anyhow,

 

 

Tried this one first.... did not seem to do anything. And the device id in system profiler was still not changed.

 

Thanks. Sorry for being such a moron about all this. I do try to read things but am one of those people who immediately looks away when they see the works 'DSDT' mentioned. Anyhow I did put back my fakeid to 0x0 in clover, and tried your 2nd suggested method 'Arbitrary'....

 

Perhaps it worked, at least I believe it worked because after reboot, near the end once its got to the point of loading GPU driver (saying 'GreenLockState...' and pausing / waiting). Well at that point its then always a hard reset. I tried also changing the 2nd byte after the 67ef to 0201 (for ati vendor id in reverse byte order).

 

If the arbitrary method you gave me has worked, but maybe for whatever reason(s) the polaris12 die is not close enough to baffin. And cannot use same baffin driver. This maybe make sense because different silicon means different number of CUs / sms / whatever. So you cannot address some of the last CUs on smaller silicon because they simply are not exist on the die.

 

Anyhow (like I said earlier)... maybe High Sierra 10.13 has a new support for polaris12 i dont know myself. Just have been avoiding trying these DP until final release is out. And as you have noticed I'm not really the smartest kid on the block to contribute with such things.

 

OK I will probably keep this card for a few days more, in case there are any other developments which need further testing. Then return the rx550 for gt1030.

 

The problem with these kexts is that almost all of them have the 0x67EF1002 definition, you may just need to keep trying them all one at a time.  And then there is the 4100, 4150, 4250 kexts which one of those is it.   If you find the right kext combo, please let us know so we can post it as fixed.  

Is there a possibility to enable graphic acceleration with

 

MB: Asus Z170 Pro Gameing

Graphiccard: MSi Radeon RX 470

 

Operating system: OS X 10.12.6

 

using lilu.kext and whatsevergreen.kext in current versions in Other-Folder of EFI/Clover ....

 

Problem:

Clover booting ends with black screen.

 

Only possibility to log in the operating system: 

In clover menu -> graphic injection -> faked 0x12345678.

But then there is no graphic acceleration

 

I placed my kexts in System/Library/Extensions folder as well as clover kext folders, in clover try no injection of ATi, no Framebuffer name, and no ID 0x0000000.     Go to clover ACPI section and select fix displays in DSDT fixes.  Try with and without fix displays.

 

Check ports DisplayPort and HDMI.     It takes a minute sometimes for the screen to appear when you have black screen wait a little to se if it pops up.   Try unplugging cable as well after a minute or so.

Share this post


Link to post
Share on other sites

In ACPI I'll try unset fix display. What do you mean by "check ports DisplayPort HDMI"? HDMI Cable is connected to HDMI-Port 1 of the graphic card to the Monitor. Also tried to change from Port 1 to Port 2, black screen persist. I'll report ...

Share this post


Link to post
Share on other sites

Gigamax - I already returned the rx550 earlier today. After learning that nothing we can do here for the time being is gonna make it work. All of these 'just change the device id', for whatever method is not gonna work. At the very minimum it would require hacking the baffin driver (rx460), to disable some of the CUs. And thats not even some guaranteed thing either. Until apple releases some new future hardware product with polaris12 inside it. Today I also asked on High Sierra thread, for which cyberdevs kindly replied and checked the newest DP seed (which itself come out just today or yesterday). In the very newest DP of 10.13, it doesnt have any references to this rx550 device id in it. Of course we did not know any other p12 device ids to check, only the 0x699f of the rx550.

Share this post


Link to post
Share on other sites

@Wardog: csrutil disable did not function :-(

@Gigmaxx: did not function :-(

 

So far, none of all the kindly supporters around the world couldn't help me, although you all have special knowledge ... thanks very much!!!

Share this post


Link to post
Share on other sites

But - and this is only cosmetic question - is it possible to hide the WhatEverGreen entries "CFG,CFG_xxx" - so that only their original entries are visable?

 

Oh, and once again: on my rig (see signature for used hardware) WhatEverGreen runs perfectly w/o any hitch. Thanx again to the guys, who made this possible after a long wait. You did a great job.

It is sort of possible, but impractical for debugging. Since it does not affect anything in a bad manner I will not look.

Share this post


Link to post
Share on other sites

Hey guys I managed to get my ryzen 10.12.6 working without helper card on my Msi rx 480(thanks go Gigamaxx) my only issue is that I have no acceleration (I'm not Injecting anything in graphics settings in clover) I tried different fb and when I get to the home screen it shows correct card number but only with a couple mb of VRAM. Any help I would appreciate it

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By kalpesh2804
      Laptop Inbuilt Wifi and Battery Indicator not working in Catalina. (HP Pavilion 15t-au 100 Laptop)
       
       
      Laptop Config:
      HP Pavilion 15t-au100 * i7-7500u 2.90Ghz * Intel HD 620 Graphic Adapter * Intel Dual Band Wireless AC-3168 * Kingston SATA3 SSD 500 GB * HP Camera
    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
      Mac Downloader (thanks to ricoc90)
       
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.14 installation on MBR HFS+ partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.14 HFS Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.14 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. Patch to stop auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.14.
      4. This patched MBR OSInstaller will never convert to APFS, and will always install as HFS+ partition.
      5. This patched MBR OSInstaller method works with both MBR HFS+ and GPT HFS+ partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version.

      How to make 10.14 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      How to make 10.14 installer for MBR (MBR-Automatic-Method)?
      Just use 14MBRinstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.13.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       


       
      Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_1014fullapp to download the full installer app via swscan.apple.com.
       

       
×