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. 

8 posts in this topic

Recommended Posts

Hello, fellow hackintosh...ers !

 

I'm coming to you with a bit of a problem that got me to scratching my head pretty bad, to the point that I now think I'm actually scratching my frontal lobe.

 

A week ago, I decided I was done with my Snow Leopard setup that was back from... well SL years. So I decided it was finally time to upgrade to a more up to date version. And what's more up to date than Mavericks DP8 ? A friend of mine running it on his iMac told me it was practically a GM, and that it was stable enough for a daily use. After a bit of research I found out some people were already running DP8 on their hackintoshes and so there was no reason to think I couldn't.

 

So I went and installed Mavericks with myHack, and the installation went very well. I had some problems with booting (Resetting IOCatalogue), spent a few days trying to resolve them, tried installing Mountain Lion instead, had the same problems, came back to Mavericks, had some problems again (mainly thinking my Radedon HD4850 was the problem), all the while learning a lot about hackintoshes and I finally was able to boot on Mavericks DP1 after using a proper DSDT file that was made for a motherboard fairly similar to mine (The DSDT file is the "F13" for a Gigabyte GA-P35-DS3R and my MB is the GA-P35-DS3).

 

Happy with my Mavericks DP1 properly booting, I decided to download a combo update to DP8 after installing the Realtek81xx kext that enabled ethernet connection and install it.

 

So now I have Mavericks DP8 installed on my computer, but when I try to boot, I get stuck with "Resetting IOCatalogue" (several minutes after the previous line, which is in most cases mounting another partition from the hard drive, right after "DSMOS has arrived"), the exact same issue I had before upgrading from DP1 to DP8, except now the solution I had for it is still in effect but the problem came back.

 

As advised on many threads, I removed every ATI, IntelHD and nVidia kext from /System/Library/Extension, in vain, the problem remains.

 

It may or may not be useful to point out that I first had a "Missing Bluetooth Controller Transport" issue that I resolved by deleting Bluetooth-related kexts (I have no use for it), and that I also added a MacPro 3,1 smbios.plist in the /Extra folder.

 

My config :

  • Gigabyte GA-P35-DS3
  • Intel Core 2 Quad Q6600
  • ATI Radeon HD4850
  • Err... that's it, pretty much.

So, what's my move ? I fortunately have a Ubuntu setup with a Mountain Lion VM from which I can access and tinker with files on my Mavericks install.

 

Thanks for reading !

 

EDIT : Oh and it goes without saying that I tried booting in safe mode, and the result was the same.

Share this post


Link to post
Share on other sites

1. Are you sure the DSDT is still in /Extra? You might have accidentally removed/moved it

2. That wasn't an error (for the bluetooth). It was telling you that it didn't find a bluetooth device on the machine. You can safely ignore that and still have the kexts installed.

3. Clover EFI, try it

Share this post


Link to post
Share on other sites

1. The DSDT is still in /Extra, no doubt about it.

2. Well maybe it isn't an error, but the boot got stuck there every time.

3. I'll look into it ;)

Share this post


Link to post
Share on other sites

2. Well maybe it isn't an error, but the boot got stuck there every time.

 

Thats because it is the very last line of a verbose boot before it hits the desktop

Share this post


Link to post
Share on other sites

I just installed the exotic patch, and as I expected it isn't the source of the problem. But that's one less thing to do afterwards anyways ;)

 

I can't seem to find the verbose boot logs. /var/logs only has system.log in which a lot of things unrelated to the boot are stored.

Share this post


Link to post
Share on other sites

I just installed the exotic patch, and as I expected it isn't the source of the problem. But that's one less thing to do afterwards anyways ;)

 

I can't seem to find the verbose boot logs. /var/logs only has system.log in which a lot of things unrelated to the boot are stored.

 

Boot into single user mode (-s) and type sudo bdmesg

 

That is a tool Chameleon uses for the logs

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.

×