Trouble with installation

[GreenT]

Hi,

I'm trying to follow the guides here, and also here because I'm using a series 200 motherboard + Kaby Lake. I got all the way through installation of Sierra. Then I ran MultiBeast, followed the recommendations, and attempted to reboot. Now, kernel panics. I've tried adjusting parameters at boot time, but the best I can get is that it gets most of the way through the boot process and then kernel panics. I've attached a photo of the verbose output.

If anybody has any idea what I'm doing wrong, please let me know.

EDIT:
Gigabyte H-270N-WiFi
Intel Core i5-7600 (Kaby Lake)
GeForce GTX 1060
8 GB RAM
PNY SATA SSD

 

[P1LGRIM]

If anybody has any idea what I'm doing wrong, please let me know.

Profiles need to contain at least your primary system to assist others with helping you

Your screenshot shows an active Serial port (SuperIO) that should be disabled in your BIOS settings.

Your Screenshot also shows that you installed the FakeSMC plugins for HW monitor and the GPU sensors element is causing the kernel panic - Delete it.

 

[GreenT]

Your screenshot shows an active Serial port (SuperIO) that should be disabled in your BIOS settings.

Will do. I apologize for the lack of system details; I had added it to my profile, but in the wrong place. It's fixed now.

Your Screenshot also shows that you installed the FakeSMC plugins for HW monitor and the GPU sensors element is causing the kernel panic - Delete it.

I installed those because it said to in jktaurus8's guide. His hardware is almost identical to mine (same motherboard and CPU). I will delete them and see how it goes.

Thank you. I really appreciate your reply.

 

[GreenT]

Your screenshot shows an active Serial port (SuperIO) that should be disabled in your BIOS settings.

I've looked through every option in my BIOS settings, and can't find one that says anything about a serial port or "SuperIO." I see one option called "IOAPIC 24-119 Entries," which can either be Enabled or Disabled. Is that it?

 

[P1LGRIM]

I've looked through every option in my BIOS settings, and can't find one that says anything about a serial port or "SuperIO." I see one option called "IOAPIC 24-119 Entries," which can either be Enabled or Disabled. Is that it?

No, that's not it - Disregard if there is no option to disable.
Your primary problem is the GPU sensors that causes your KP in Sierra.

 

[GreenT]

No, that's not it - Disregard if there is no option to disable.
Your primary problem is the GPU sensors that causes your KP in Sierra.

I deleted the FakeSMC stuff, and no more kernel panics.

But I'm having problems now with my display and graphics drivers.

1. If I boot in normal mode, it goes through most of the boot and then the screen goes dark. This is happening because the monitor doesn't detect a signal from the GPU and goes into power-save mode, even though the computer is active. (Or, at least I think it's active. But no amount of keypresses or mouse movement wakes the monitor. I have to hard reset it.)

2. I can get around problem #1 by booting in verbose mode -- it makes it through the entire boot process with the monitor awake. But then the display is screwed up. If I try to enable the NVIDIA Web Driver, it seems like it's enabled and tells me it has to restart. But after the restart it's still using the OS X Default Graphics Driver. My display is 1920x1200, but macOS think's it's a 1600x1200 pixel display, and won't let me change resolution.

Any advice would be appreciated.

 

[cmn699]

I deleted the FakeSMC stuff, and no more kernel panics.

But I'm having problems now with my display and graphics drivers.

1. If I boot in normal mode, it goes through most of the boot and then the screen goes dark. This is happening because the monitor doesn't detect a signal from the GPU and goes into power-save mode, even though the computer is active. (Or, at least I think it's active. But no amount of keypresses or mouse movement wakes the monitor. I have to hard reset it.)

2. I can get around problem #1 by booting in verbose mode -- it makes it through the entire boot process with the monitor awake. But then the display is screwed up. If I try to enable the NVIDIA Web Driver, it seems like it's enabled and tells me it has to restart. But after the restart it's still using the OS X Default Graphics Driver. My display is 1920x1200, but macOS think's it's a 1600x1200 pixel display, and won't let me change resolution.


Any advice would be appreciated.

You do need FakeSMC.kext because it is a Mandatory kext for Hackintosh function. The version you had installed before which caused KP during boot was not the right one you needed. Try installing this I am uploading as compressed and see if it would make any difference.

 

[macs_forever]

I deleted the FakeSMC stuff, and no more kernel panics.

But I'm having problems now with my display and graphics drivers.

1. If I boot in normal mode, it goes through most of the boot and then the screen goes dark. This is happening because the monitor doesn't detect a signal from the GPU and goes into power-save mode, even though the computer is active. (Or, at least I think it's active. But no amount of keypresses or mouse movement wakes the monitor. I have to hard reset it.)

2. I can get around problem #1 by booting in verbose mode -- it makes it through the entire boot process with the monitor awake. But then the display is screwed up. If I try to enable the NVIDIA Web Driver, it seems like it's enabled and tells me it has to restart. But after the restart it's still using the OS X Default Graphics Driver. My display is 1920x1200, but macOS think's it's a 1600x1200 pixel display, and won't let me change resolution.

Any advice would be appreciated.

Also, you need the Clover version with NVRAM emulation for your web drivers and select the Nvidia web drivers option in MultiBeast.

 

[GreenT]

You do need FakeSMC.kext because it is a Mandatory kext for Hackintosh function. The version you had installed before which caused KP during boot was not the right one you needed. Try installing this I am uploading as compressed and see if it would make any difference.

FakeSMC.kext was not causing the kernel panic. I didn't remove that. It was the FakeSMC GPU plugin that was causing the panic. I removed all of the plugins, but I left the FakeSMC.kext in place. The one I have is newer than the one you uploaded, and it's working fine.

Also, you need the Clover version with NVRAM emulation for your web drivers and select the Nvidia web drivers option in MultiBeast.

I had already done this. I just did it again, and I'm still having the same problems. Have to boot in verbose mode or the signal from the GPU is lost, and when I select the NVIDIA web drivers in Sierra, the setting reverts to OS X Default Graphics Driver after reboot.

 

[cmn699]

FakeSMC.kext was not causing the kernel panic. I didn't remove that. It was the FakeSMC GPU plugin that was causing the panic. I removed all of the plugins, but I left the FakeSMC.kext in place. The one I have is newer than the one you uploaded, and it's working fine.



I had already done this. I just did it again, and I'm still having the same problems. Have to boot in verbose mode or the signal from the GPU is lost, and when I select the NVIDIA web drivers in Sierra, the setting reverts to OS X Default Graphics Driver after reboot.

I misread or read into what you posted about "FakeSMC stuff".
One other point: have you made in config.plist>Graphics [

] Inject NVidia, if "True", make it "False" and see.