Contribute
Register

Having Problems Using the Direct Update to macOS Sierra using Clover Method

Status
Not open for further replies.
Joined
Aug 25, 2016
Messages
20
Motherboard
ASUS Z170-A
CPU
i5-6600k
Graphics
None
Mac
  1. MacBook Pro
Hi all, I pretty much read through most posts here but could not find similar issues, here I am stuck here seeking for help:

I followed the following steps:
  1. Updated Clover to r3773. Rebooted fine.
  2. Grabbed a copy of FakeSMC.kext from System/Library/Extensions/, and copied to EFI/EFI/Clover/kexts/Other
  3. Launched Sierra installer. System rebooted.
  4. Selected "Boot from Mac Os installer" at Clover boot screen - no caches, w/kexts
  5. During the loading at apple logo screen, I get the following message from verbose mode:
    - looks like it has to do with intel integrated graphic , I have no GPU and just use i5-6600k cpu, I believe its HD530?
I repeated step 1~5 , with variety of clover boot option at step 4, with or without caches, with or without kexts, none of combination has worked yet. Has anyone ran into similar issue?
 

Attachments

  • Photo 2016-10-02.png
    Photo 2016-10-02.png
    1.5 MB · Views: 322
Has anyone ran into similar issue?

Yes, similar KP to yours, or at least involving IOAcceleratorFamily2. I also have Skylake proc, but in a NUC. I use RehabMan's Hotpatch method and there was a missing KextsToPatch entry that caused the problem. I guess this is only relevant if you are using a similar build method? Can look into it some more if you are still having issues and using a similar installation method?
 
Yes, similar KP to yours, or at least involving IOAcceleratorFamily2. I also have Skylake proc, but in a NUC. I use RehabMan's Hotpatch method and there was a missing KextsToPatch entry that caused the problem. I guess this is only relevant if you are using a similar build method? Can look into it some more if you are still having issues and using a similar installation method?

Hi Andy, thanks for your reply. Thank god that someone has seen similar issue.

Yes, I'm still having exact same kernel panic message; IOgraphics Flag, AppleIntelSKLGraphicsFramebuffer, IOPCIFamily, and so forth.

- I tried changing the SMBIOS from imac14,2 and Mac Pro 6,1 but both shows same kernel panic message including those keywords and I believe it has nothing to do with SMBIOS.

Unfortunately, my build is not based on Rehabman's Hotpatch or anything fancy like NUC, just a regular ATX mobo (i.e. asus z170-a) with i5-6600k, followed by Tonymac guide on installing EI Capitan in common way.

I'm sort of feeling hopeless now, thinking of giving it another week until I find someone who resolved this issue from here, or might as well do fresh Sierra install :(
 
I tried changing the SMBIOS from imac14,2 and Mac Pro 6,1 but both shows same kernel panic message including those keywords and I believe it has nothing to do with SMBIOS.

Unfortunately, my build is not based on Rehabman's Hotpatch or anything fancy like NUC, just a regular ATX mobo (i.e. asus z170-a) with i5-6600k, followed by Tonymac guide on installing EI Capitan in common way.

So I don't really know enough to help! I have taken out the config.plist changes I made (or at least those that appear graphics related) and of course everything continues to work. I think the kext patches are cached (could be wrong) so that might be why. I spent so long getting it to work that I'm currently don't have further time to experiment trying to recreate the problem. But you could try this in the KextsToPatch section of config.plist (In KernelAndKextPatches section)

<dict>
<key>Comment</key>
<string>Boot graphics glitch, 10.12.dp1 (credit denskop)</string>
<key>MatchOS</key>
<string>10.12.x</string>
<key>Find</key>
<data>AQAAdSU=</data>
<key>Name</key>
<string>IOGraphicsFamily</string>
<key>Replace</key>
<data>AQAA6yU=</data>
</dict>

In Xcode it should look like:

Item#
Comment String Boot graphics glitch, 10.12.dp1 (credit denskop)
MatchOS String 10.12.x
Find Data <01000075 25>
Name String IOGraphicsFamily
Replace Data <010000eb 25>


I use iMac14,2
 
So I don't really know enough to help! I have taken out the config.plist changes I made (or at least those that appear graphics related) and of course everything continues to work. I think the kext patches are cached (could be wrong) so that might be why. I spent so long getting it to work that I'm currently don't have further time to experiment trying to recreate the problem. But you could try this in the KextsToPatch section of config.plist (In KernelAndKextPatches section)

<dict>
<key>Comment</key>
<string>Boot graphics glitch, 10.12.dp1 (credit denskop)</string>
<key>MatchOS</key>
<string>10.12.x</string>
<key>Find</key>
<data>AQAAdSU=</data>
<key>Name</key>
<string>IOGraphicsFamily</string>
<key>Replace</key>
<data>AQAA6yU=</data>
</dict>

In Xcode it should look like:

Item#
Comment String Boot graphics glitch, 10.12.dp1 (credit denskop)
MatchOS String 10.12.x
Find Data <01000075 25>
Name String IOGraphicsFamily
Replace Data <010000eb 25>


I use iMac14,2

Hey Andy, huge thanks to you once again for providing me help. Unfortunately, same message pops up and at this point, I don't think anyone else had the exact same issue; I don't see anyone else complaining about this guide with kernel panic on i5 6600k skylake integrated graphic card.

Now, to ALL the folks who had issues with this direct update guide, can we just create a new Mac OS Sierra installer bootable USB with the new Unibeast that just released, and choose "Upgrade" on EI Capitan instead of clean install?

Thanks and please let me know if anyone has done this way rather than direct update, and any error if you encountered.
 
Update on this post,

so after using the unibeast method of installing Mac OS Sierra, now I was able to install (i.e. upgrade not clean install) and using it since then.

However, I'm not able to boot into Mac OS Sierra without the bootable unibeast USB. If I choose to boot into Mac OS Sierra, I get the following error.

Any help on this kernel panic message would be great.. thanks

PS: I tried patching the intel HD 530 through the new multibeast but that still didn't help.

Sat Oct 8 17:11:37 2016

*** Panic Report ***
panic(cpu 3 caller 0xffffff7f8219e05c): assertmsg@/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-10.18.65/Common/IONDRV/Intel/SKL/AppleIntelFramebuffer/AppleIntelController.cpp:25445
Backtrace (CPU 3), Frame : Return Address
0xffffff93b53c3cc0 : 0xffffff80002f748c
0xffffff93b53c3d40 : 0xffffff7f8219e05c
0xffffff93b53c3db0 : 0xffffff7f8219aea2
0xffffff93b53c3e40 : 0xffffff800089bdcd
0xffffff93b53c3e80 : 0xffffff800089bb1e
0xffffff93b53c3f10 : 0xffffff800089b0d6
0xffffff93b53c3f60 : 0xffffff800089caee
0xffffff93b53c3fb0 : 0xffffff80002a6af7
Kernel Extensions in backtrace:
com.apple.driver.AppleIntelSKLGraphicsFramebuffer(10.1.8)[79FA4A62-0C04-31CC-87EC-2F6FF665DD48]@0xffffff7f82174000->0xffffff7f82320fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[731443D8-78D5-30C8-939A-1ED3E857CA22]@0xffffff7f80b82000
dependency: com.apple.iokit.IOACPIFamily(1.4)[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7f80ca7000
dependency: com.apple.iokit.IOAcceleratorFamily2(288.13)[27E0AFCE-E36A-35F5-A008-BB1EB3A2C7B9]@0xffffff7f820c8000
dependency: com.apple.iokit.IOReportFamily(31)[3CAF0CDE-3EB5-32C8-91EF-EC5C7CAFBA22]@0xffffff7f8186a000
dependency: com.apple.AppleGraphicsDeviceControl(3.13.60)[FDEAB5E1-3BFF-34DF-92AB-6AE26C8405F7]@0xffffff7f82168000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[377FAA09-C02F-3FF4-A5DE-C0F2E711C8B0]@0xffffff7f81909000

BSD process name corresponding to current thread: kernel_task
Boot args: -v -x
 
Update on this post,

so after using the unibeast method of installing Mac OS Sierra, now I was able to install (i.e. upgrade not clean install) and using it since then.

However, I'm not able to boot into Mac OS Sierra without the bootable unibeast USB. If I choose to boot into Mac OS Sierra, I get the following error.

Any help on this kernel panic message would be great.. thanks

PS: I tried patching the intel HD 530 through the new multibeast but that still didn't help.

Sat Oct 8 17:11:37 2016

*** Panic Report ***
panic(cpu 3 caller 0xffffff7f8219e05c): assertmsg@/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-10.18.65/Common/IONDRV/Intel/SKL/AppleIntelFramebuffer/AppleIntelController.cpp:25445
Backtrace (CPU 3), Frame : Return Address
0xffffff93b53c3cc0 : 0xffffff80002f748c
0xffffff93b53c3d40 : 0xffffff7f8219e05c
0xffffff93b53c3db0 : 0xffffff7f8219aea2
0xffffff93b53c3e40 : 0xffffff800089bdcd
0xffffff93b53c3e80 : 0xffffff800089bb1e
0xffffff93b53c3f10 : 0xffffff800089b0d6
0xffffff93b53c3f60 : 0xffffff800089caee
0xffffff93b53c3fb0 : 0xffffff80002a6af7
Kernel Extensions in backtrace:
com.apple.driver.AppleIntelSKLGraphicsFramebuffer(10.1.8)[79FA4A62-0C04-31CC-87EC-2F6FF665DD48]@0xffffff7f82174000->0xffffff7f82320fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[731443D8-78D5-30C8-939A-1ED3E857CA22]@0xffffff7f80b82000
dependency: com.apple.iokit.IOACPIFamily(1.4)[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7f80ca7000
dependency: com.apple.iokit.IOAcceleratorFamily2(288.13)[27E0AFCE-E36A-35F5-A008-BB1EB3A2C7B9]@0xffffff7f820c8000
dependency: com.apple.iokit.IOReportFamily(31)[3CAF0CDE-3EB5-32C8-91EF-EC5C7CAFBA22]@0xffffff7f8186a000
dependency: com.apple.AppleGraphicsDeviceControl(3.13.60)[FDEAB5E1-3BFF-34DF-92AB-6AE26C8405F7]@0xffffff7f82168000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[377FAA09-C02F-3FF4-A5DE-C0F2E711C8B0]@0xffffff7f81909000

BSD process name corresponding to current thread: kernel_task
Boot args: -v -x

Update: Now I have working Mac OS Sierra and for those of you who may need guide in solving this or any other kernel panic, please follow the step below, I simply swapped the entire EFI in Sierra installed drive by the fresh batch from the bootable USB then it worked like charm.

1. Follow Tony guide on creating bootable USB. Plug the USB and reboot.
2. boot into Sierra using Bootable USB.
3. Mount the EFI Partitions from Sierra and Bootable USB
4. Copy over (overwrite) the entire EFI folder from Bottable USB into the Sierra installed drive.
>> Note: do not get rid of the "APPLE" folder. Not sure if anyone else have this folder either but I left this folder untouched
5. Remove the Bootable USB and Reboot.
6. Boot into Sierra drive this time. Now use multibeast in installing all your patches as you need
 
Hi all, I pretty much read through most posts here but could not find similar issues, here I am stuck here seeking for help:

I followed the following steps:
  1. Updated Clover to r3773. Rebooted fine.
  2. Grabbed a copy of FakeSMC.kext from System/Library/Extensions/, and copied to EFI/EFI/Clover/kexts/Other
  3. Launched Sierra installer. System rebooted.
  4. Selected "Boot from Mac Os installer" at Clover boot screen - no caches, w/kexts
  5. During the loading at apple logo screen, I get the following message from verbose mode:
    - looks like it has to do with intel integrated graphic , I have no GPU and just use i5-6600k cpu, I believe its HD530?
I repeated step 1~5 , with variety of clover boot option at step 4, with or without caches, with or without kexts, none of combination has worked yet. Has anyone ran into similar issue?

Hey I'm having the same exact kernel panic. How did you upgrade using a usb without having to do a clean install?
 

Attachments

  • IMG_0569.JPG
    IMG_0569.JPG
    3 MB · Views: 133
Hey I'm having the same exact kernel panic. How did you upgrade using a usb without having to do a clean install?

As usual, please provide detailed info on how/when/where you got this kernel panic message otherwise I can't be much help :).
I'd assume you have perfectly working EI Capitan. I simply followed the Tony's Sierra unibeast method to upgrade from EI Capitan to Sierra. You simply skip the steps where the guide instructs user to format the drive for clean install.

Now I'm beginning to think that this KP is specific to ASUS mobo given multiple users who have used my method to solve this issue had ASUS Mobo. After you've succeeded in upgrading, you're likely going to get HD530 flickering issue as well unless you have GPU. So I'd say if this is critical, you might as well wait until HD530 issue is solved.
 
As usual, please provide detailed info on how/when/where you got this kernel panic message otherwise I can't be much help :).
I'd assume you have perfectly working EI Capitan. I simply followed the Tony's Sierra unibeast method to upgrade from EI Capitan to Sierra. You simply skip the steps where the guide instructs user to format the drive for clean install.

Now I'm beginning to think that this KP is specific to ASUS mobo given multiple users who have used my method to solve this issue had ASUS Mobo. After you've succeeded in upgrading, you're likely going to get HD530 flickering issue as well unless you have GPU. So I'd say if this is critical, you might as well wait until HD530 issue is solved.

Okay thanks for making me aware of the issues. I think for now i'll stay on my el capitan until these bugs are fixed. I rely too heavily on my system to have any downtime
 
Status
Not open for further replies.
Back
Top