Contribute
Register

Infinite Boot Loop 10.12.5 > 10.12.6 Update

Joined
Jun 22, 2017
Messages
49
Motherboard
Gigabyte GA-Z170MX-Gaming 5
CPU
Intel i7-6700K
Graphics
MSI GTX 1070 AERO 8G OC
Alright. I've tried your suggestions.

1) I have no USB fixes in place that I am aware of or manually configured. When I used the Fix USB flag nothing changed.

2)The first command came up with this:

After the second command I get this:

It is currently hanging there now. Should I hit the hardware switch to reset now and then try a normal boot or single user boot? Thank you.
 

P1LGRIM

Moderator
Joined
Mar 2, 2012
Messages
21,732
Motherboard
Lenovo ThinkStation p300 ⌘
CPU
i7-4790K
Graphics
HD 4600
Mac
MacBook Pro, Mac mini
Classic Mac
Power Mac
Mobile Phone
iOS
Carbon copy cloner, you can't have enough bootable backup drives when things break.
I have clones of all of my (10) hacks.
I use a hardware disk cloner - One button press and it's done.
 
Joined
May 15, 2016
Messages
4,852
Motherboard
GIGABYTE Z170M D3H
CPU
i5-6500
Graphics
RX 480
Mac
iMac
Alright. I've tried your suggestions.

1) I have no USB fixes in place that I am aware of or manually configured. When I used the Fix USB flag nothing changed.

2)The first command came up with this:

After the second command I get this:

It is currently hanging there now. Should I hit the hardware switch to reset now and then try a normal boot or single user boot? Thank you.
yes, try reboot use nv_disable=1 you probably don't have web drivers working yet.

Also, what about Skylake Graphics? 12.6 requires new fixes for IGPU.
 
Joined
Jun 22, 2017
Messages
49
Motherboard
Gigabyte GA-Z170MX-Gaming 5
CPU
Intel i7-6700K
Graphics
MSI GTX 1070 AERO 8G OC
I rebooted my machine and tried both a normal boot and a single user boot with the no change from my original issue. Did the screenshots I posted last illuminate anything? To me it seemed everything was being read properly from the NVMe drive when I ran "fsck -fy" but upon running "exit" it hung up. Thanks!
 
Joined
Jun 22, 2017
Messages
49
Motherboard
Gigabyte GA-Z170MX-Gaming 5
CPU
Intel i7-6700K
Graphics
MSI GTX 1070 AERO 8G OC
The "nv_disable=1" boot flag didn't change anything. When I run that I get exactly the screen I got in my OP. Do you want me to plug in my HDMI cable to my onboard port or something?
 
Joined
Jul 16, 2012
Messages
44
Motherboard
Asus Zen Book UX430UA
CPU
i7 8550
Graphics
620 UHD
Mac
MacBook Air, MacBook Pro
Mobile Phone
Android, iOS, Other
How do you have NVMe configured? Are you using the HackerNVMe kext or are you putting edits in the config.plist?
 
Joined
May 15, 2016
Messages
4,852
Motherboard
GIGABYTE Z170M D3H
CPU
i5-6500
Graphics
RX 480
Mac
iMac
You may need to. Hold " delete" key at start up, go to bios and enable IGFX or IGPU and allocate 64mb memory. Connect cable to mobo.

Unplug your power pins for Nvidia card, then boot up and stop,at clover menu screen. Scroll to options then go to graphics settings. Use Inject Intel, fake ID 0x0000000, ig 0x19120001, look for your Nvidia card it should no lnger show if power pins are disconnected (you don't need to remove the card).

Try this and see if you still get kernel panic.
 
Joined
Jun 22, 2017
Messages
49
Motherboard
Gigabyte GA-Z170MX-Gaming 5
CPU
Intel i7-6700K
Graphics
MSI GTX 1070 AERO 8G OC
I am using RehabMan's patch procedure which uses the HackerNVMe kext.
 
Joined
Jun 22, 2017
Messages
49
Motherboard
Gigabyte GA-Z170MX-Gaming 5
CPU
Intel i7-6700K
Graphics
MSI GTX 1070 AERO 8G OC
I tried everything you said about switching to my onboard GPU. Zero change. I think it has to do with NVMe drive based on what people are saying with similar issues. Thank you for the help though.
 
Joined
May 15, 2016
Messages
4,852
Motherboard
GIGABYTE Z170M D3H
CPU
i5-6500
Graphics
RX 480
Mac
iMac
I tried everything you said about switching to my onboard GPU. Zero change. I think it has to do with NVMe drive based on what people are saying with similar issues. Thank you for the help though.
-x or safe mode with the IGPU settings?


I forgot one thing for -s at root type"mount -uw" root# "fsck -fy" then "exit". The mount command may address the nvme issue?
 
Top