Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Vermoot

Members
  • Content count

    4
  • Joined

  • Last visited

About Vermoot

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL
    http://www.vermoot.com
  • Skype
    Rougemoot

Profile Information

  • Gender
    Male
  • Location
    France
  • Interests
    Musicmaking, comic books
  1. @memomo: I had the exact same problem and spent a long time trying to understand what was going on. Turns out what fixed the problem was simply updating vmware from 6.0.1 to the latest version, 6.0.3, as simple as that. Let me know if it did it !
  2. 10.9 DP8 : Resetting IOCatalogue

    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.
  3. 10.9 DP8 : Resetting IOCatalogue

    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
  4. Well look who it is

  5. 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.
×