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.


  • Content count

  • Joined

  • Last visited

About froglegs

  • Rank
    InsanelyMac Protégé
  1. I might have been unclear about a few things so here's a more "to the point" post: Any components in a hackintosh that apple actually uses in some of their current systems, will be recognized and properly installed by OSX in the hackintosh system, correct? Problems arise when you use components that aren't found in any of the systems sold by apple (for example, when building a 2013 Mac Pro hackintosh, using an X79 based Motherboard instead of a C602J based motherboard like the actual Mac Pro)? There are plenty of examples of people carefully selecting the components for their iMac / Mac Mini hackintosh systems and these systems are 100% perfectly functional (if it weren't for the bootloader you'd never know it was a hackintosh). I can't find any examples of people doing this with the 2013 Mac Pro though (as I said, everybody uses Intel's X79 platform instead). I realize there aren't very many first hand experiences out there. I don't mind taking a little risk and being the first one to test this out. I just don't want to waste my time and money on a complete lost cause (there's something I'm missing and this system will most likely have the same problems that the X79 / 4930K systems have).
  2. Most of the high end Mac Pro hackintosh builds are using Intel's enthusiest platform (i.e. X79 chipset, 3930K / 4930K processor). Since Apple doesn't use these components in any of their systems, it can be difficult to get everything functioning properly. I did a bit of reading to figure out what exactly Apple uses in the new Mac Pro. It's pretty well known that Apple uses the Xeon E5 v2 processor (E5-1620 v2, E5-1650 v2, E5-1680 v2 and E5-2697 v2 for the 4-core, 6-core, 8-core and 12-core options respectively). I also confirmed that Apple uses the Intel C602J chipset in the 4-Core model (I couldn't confirm that the same chipset is used with the other 3 processors but I assume that it is). Regardless of the exact brand / model motherboard you use, as long as the motherboard uses the C602J chipset, the majority of onboard devices should be identical and thus supported by OSX, correct? Obviously depending on the exact model, the 3rd party additions such as USB 3.0, additional SATA controllers and on-board audio will differ and may not be supported but you can just disable these in the BIOS. If I built a computer using one of the above Xeon E5 v2 processors and a C602J based motherboard, it should work right out of the box shouldn't it? I'd obviously hand pick the rest of the hardware as well (audio, video, wireless networking, bluetooth, additional SATA / USB controllers, thunderbolt) for compatibility with OSX. It seems though, that the most important factors determining overall functionality of the system are the CPU and the motherboard / chipset. Like I said, there is no shortage of information pertaining to X79 builds but I can't find much info on builds that use the exact components used in the 2013 Mac Pro and if using the exact processor and chipset (as opposed to an X79 based system) would solve the problems associated with the X79 systems. Any suggestions / experiences are greatly appreciated. Thanks
  3. Thanks a bunch for the info. I initially tried resetting the CMOS and it didn't remove the extra drives. Along these same lines though, I ended up re-flashing the BIOS and this finally solved the problem. My ASUS board has the CMOS reset button on the back and I feel like this doesn't completely reset everything. I'm just glad I didn't mess anything up too badly (was starting to worry it might be something permanent). Anyway, thanks again for the help.
  4. I've been messing around with Yosemite and in the process of trying to get everything working, I've reinstalled the OS multiple times. I noticed a bunch of bootable partitions in my BIOS (ASUS Rampage IV Formula) but figured they were just recovery partitions or something. I just did a complete wipe of my hard drive to remove them (wrote zeros to the entire drive using a bootable linux distro) and they still show up. I don't have anything else plugged into the computer (no external USB drives or thumb drives) and there's only 1 internal hard drive. I feel like I'm doing something incredibly stupid / missing something obvious but I can't seem to figure it out. I used Clover to install Yosemite. I've been using Clover for awhile though and never had this problem in the past. Does anybody know what might be causing this?
  5. Full Resolution at Clover

    Using Legacy boot settings (as opposed to UEFI). When you initially install clover, at the "customize" menu, I originally used the option "Install for UEFI booting only." To use legacy settings, select the "Install boot0af in MBR" option under "Bootloader" (be sure to leave "Install for UEFI booting only" unchecked). I'm not sure what motherboard you're using, but you should see two boot options (one that lists the boot device prefaced by "UEFI" and a second with UEFI omitted). Selecting the option with UEFI ommited (along with legacy settings) fixes the resolution for me.
  6. Full Resolution at Clover

    I had the same problem with my R9 290X when using UEFI boot mode. To solve an unrelated issue, I ended up reinstalling clover using Legacy settings and it had the side effect of fixing the clover boot resolution (2560x1080 on my U2913WM).
  7. R9 290X Help for mavericks

    I finally found some time to do a fresh install of Mavericks and try out the package netkas linked a few pages back. Thanks netkas for your hard work and for sharing the package with everybody. I tried it with both 10.9.3 and 10.9.4 and my Sapphire 290x worked fantastic in both cases. The only issue I ran into had to do with me running dual 290x cards. I'm using a Rampage IV Formula motherboard with a 290x in the first and third PCI slots. When my monitor was connected to the card in the first slot, at first I wouldn't get any video at all and after playing around with it a bit, I'd finally get video but it would be very distorted (my dell monitor gave me an error message saying the current input timing is not supported). All I had to do was swap the monitor to the card in the third PCI slot and it immediately worked perfectly though. Not sure what exactly is causing this but figured I'd mention it in case somebody else is having the same problem.
  8. R9 290X Help for mavericks

    To those of you that have used the 10.10 290x kexts in 10.9.3, how well is it working for you? I've tried both 10.10 and 10.9.3 (with the 10.10 kexts). I have a pair of 290x cards in the computer and they are both immediately recognized in 10.10. I'm using a 29" (2560x1080) monitor and the monitor and resolution are both recognized. When I first install 10.9.3 (without 10.10 kexts), Mavericks defaults to the correct resolution (2560x1080) but the monitor model isn't shown and cards are listed as generic AMD with 10mb vram. Graphics are a bit jittery and flash video doesn't work. After I install the 10.10 kexts in 10.9.3, both 290x cards are shown correctly with 4096mb vram. The exact model of my monitor now correctly appears as well (as it did in 10.10). This appears to be purely cosmetic though because I'm getting the same jittery performance / no video playback that I got prior to installing the kexts. If anybody has had more success, I'd love to know what you did. Also, has anybody gotten flash video to work in 10.10? If I could get a few bugs worked out in 10.10 I'd probably just upgrade to it permanently (it actually isn't too bad for a beta release).
  9. I'm guessing that your new install overwrote your power management kexts with the default apple ones. If you are able to do a 10.8.2 clean install I would imagine this would solve the problem. If those power management kexts aren't in place when you reboot, you'll get constant kernal panics and won't be able to get into the OS. You can also try reverting back to your old install and make sure you replace the necessary kexts BEFORE you reboot your computer after installing. There are also ways to modify these kexts through terminal using your thumb drive but I'm not familiar with exactly how to do this. Maybe somebody else can help you.
  10. After messing around with the computer for a few hours the computer is still doing the same thing. For the first 10 or 15 minutes after I boot up, disk utility works just fine. Then for no apparent reason it just doesn't work anymore. It doesn't seem to be linked to any specific application. Anybody have any other suggestions? This is driving me crazy.
  11. Since you seem to be getting multiple errors all I can do is suggest a few common solutions to those errors. GraphicsEnabler=No can often times solve the problem with the blank screen. Boot from your ###### USB drive and use GraphicsEnabler=No. If this solves the problem you can run ###### check this option. "Waiting on root device" usually means the USB port you have your flash drive in has stopped working. If you get this error while booting from your flash drive, try using a different USB port. Issues with CPU power management can also cause the computer to freeze up, kernal panics etc. I'm not familiar with your motherboard but you likely need either NullCPUPowerManagement or the patched AppleIntelCPUPowerManagement.kext. When you installed the update it's likely that one of these was overwritten and this would cause your problems.
  12. Thanks, I really appreciate the suggestions. I installed Onyx so I can repair disk permissions when disk utility stops working. I also redid all my SATA connections. Right now disk utility is working but I haven't been able to recreate exactly what it is that causes it to stop working. I'll just have to mess around with the computer for a few hours and see if disk utility is still working after I'm done. I tried launching every program individually to see if it was any one program that was causing the problem. Disk utility was still working so it must be a combination of things. Hopeully it was a connection issue cause that would make sense. Anyway, thanks again for the responses. I'll post back later today with an update.
  13. SSD maintenance?

    If you have TRIM enabled you should be all set. The only other things you can do (or not do for that matter); you don't need to defrag an SSD and you can try to limit how many times you rewrite to the drive (i.e. don't reinstally the OS every day). Stuff like that will shorten the life as you only have so many rewrites you can do. For the most part though, unless you're doing something insane this shouldn't be an issue. By the time the drive starts to die due to rewrites you'll have upgradded it to something newer, faster, larger and cheaper.
  14. I installed OSX on my PC for the first time a few days ago. I've ironed out most of the kinks and have everything running great aside from this issue with disk utility. When I first log in to OSX (10.8.2) disk utility works fine. If I do other things before using disk utility and then open up disk utility later, it freezes up with a spinning beachball and I have to force quit. The only way I can gain access to it is to restart the computer and use it right when I boot up. My system specs are as follows: Motherboard: ASUS P8Z77-V Processor: Intel Core-i7 2700K Video Card: ASUS GTX 660 Ti Memory: Corsair Vengeance 8GB @ 1600Mhz Hard Drive 1: Samsung 830 128GB SSD Hard Drive 2: Western Digital Blue 1TB If anybody has any idea what might be causing this I'd really appreciate any suggestions. I'm willing to try anything as I'm pretty lost at this point. Thanks