Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
Joe Crozier

Unable to boot installer for Haswell/Intel 4600 laptop on 10.8.5

5 posts in this topic

Recommended Posts

Hi everyone,

I'm having an issue with a friend's laptop. 

The specs are as follows:

Intel Core i7-4700MQ
Motherboard: W230ST
16 GB DDR3
Intel HD 4600 integrated
Nvidia GTX 765M dedicated

As far as I understand, we'll be unable to to use Nvidia card, this is fine, he's okay with using integrated graphics instead.

I used a typical method posted on another site (I'm sure you can guess) to create an installer USB. I have not edited it further, it has all the default kexts/boot flags.

When using verbose boot, it is clear the installer will never fully load. Instead, it will hang on 
"[iOBluetoothHCIController][start] -- completed" 

From what I've read, this suggests that the issue is not related to Bluetooth, but in fact the graphics card. Apparently it is able to load the installer, but freezes when trying to use the graphics card to display the install screen.

I have tried nearly every combination of boot flags, PCIRootUID, npci, -v, -f, -x, GraphicsEnabler (Yes and No), IntelAzulFB=1-15, and several others. 

Safe mode boot does not work (hangs in the same spot). Single user mode will work, allowing me to manipulate folders and move kexts around. Based on others' suggestions, I have removed all AppleIntelHD* and AppleIntelF* kexts. 

I've read countless forum posts from people with a similar issue, unfortunately to no avail. It appears as if most people are able to boot into safe mode, which I am not.


I'm effectively at my wits end, I'm no newbie to hackintosh but this problem has me stumped.

If anyone has any ideas as to what I could be missing, I would greatly appreciate any help.

Thanks very much!

Joe

Share this post


Link to post
Share on other sites

Thanks for the reply!

 

I actually followed that exact post when patching the kernel. I've double checked and I'm confident I followed the instructions correctly; I believe the problem exists outside the kernel.

 

Do you have any other ideas?

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.

×