Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by ^Andy^

  1. With all due respect that's a bit of a silly comment. There are so many people who have contributed in so many different areas of the hackintosh project that it's almost if not entirely impossible to avoid using other peoples work. It's also not always possible to credit the people who's work you are using because 9 times out of 10 you simply don't know who has contributed and how far back those contributions go.
    Not looking to be flamed so if you don't agree please just ignore :)


  2. This is one of the misconceptions that I had in mind.  With a socket 2011 motherboard, which has largely been out concurrently with socket 1155 (the motherboard discussed in this thread), you can have up to 6 PCI-e x16 lanes on a 1P build or up to 7 PCI-e lanes on a 2P build.


    Even if you do color grading, which is the most PCI-e intensive application one can do, you can do it with 6 PCI-e x16 lanes.  Because you have all of those built into your $360 motherboard you do not need to spend an extra $750 on a TB to PCI-e chassis or TB to X adapters.  Every single PCI-e card you might stick in that TB chassis can go internal.  It saves you time and it saves you money to just use a workstation motherboard.  That is my point.


    I do understand that you receive data on TB drives sometimes.  If you need TB purely to transfer files to the network then have a Mac Mini do it.  Hopefully there will be PCI-e TB cards out for hacks eventually, but even if they are not hot swappable it really makes little difference.  TB is not as useful or as efficient of an option as a motherboard with PCI-e lanes available.




    Secondly, you do not need to buy a new computer every year--you just need to buy the correct computer when you buy one (not necessarily the last socket to be released).  socket 2011 and socket 1155 both came out in 2011, granted there was a 6 month spread between them with 1155 being first.  Buying a socket 1155 now, in Q3 2013, after it is EOL is a decidedly questionable decision. 


    Especially so, because if you are in a professional industry that needs more than 32GBs RAM, more CPU power than an i7-Quad Core, or lots of PCI-e slots (or might need these in the next 3-4 years) then you are shooting yourself in the foot with this motherboard or even with a Haswell socket 1150.  Those are iMac's in disguise.  


    You should have bought a socket 1366 in 2009-mid 2011, then bought a socket 2011 if purchasing in 2011 Q3 until Q4 2014.

    Absolutely everything you have said here confirms my confusion over the new mac pro and it's absurd new design. I always wanted a mac pro until they announced the new pedal bin shaped one :(

  3. Awesome work as usual Andy! How many of the DP updates have you applied? DPs 1 through 5 worked fine for me, but when I updated to 6 it kernel panics on every boot except when booting using the install drive (even though they have the same kexts!) I'll try again and see what happens.

    All of them including dp6, only ever had a kernel panic if I use mac pro in the smbios which causes a KP until I delete AppleTYMCE.


    I'm going to have a go at creating some instructions using Pandora's box when I get a chance - Have to support these guys because it looks like a very handy installer and should make the install a lot simpler.

    Also, I wanted to use the onboard (P8P67 Pro v3.0) ALC892 audio, but the included AppleHDA didn't work. This is solved by downloading the multiple beast-flavoured software (version 5.43 for ML) and installing only the Drivers > Audio > Realtek ALC8xx > Without DSDT > ALC892 kext and rebooting.


    I hope all these posts will help someone! Again, brilliant work Andy :)

    Thanks I'll be sure to update the AppleHDA kext before I try my Pandora's box experiments :)

  4. Hmm, might be a bit early for that. in our industry (film and post production) its caught on quite well already. And if the new mac pro doesn't flop that will push it even harder into some markets. Granted it seems likely to stay a pro / high-end interface for the near to mid term but once intel integrates it directly onto the CPU it may still become more ubiquitous. USB 3.0 is great for as an external drive connector. But for attaching SAS RAIDS, 10GbE, and other hardware that used to require PCIe cards TB is quite useful. I think this tech has legs but time will tell. There seems to be a lot of misunderstanding about what thunderbolt is for right now. Apple gets it (maybe TOO much) but intel is in a very good position to keep it alive and pushing it along since it makes the chips and chipsets we all use and it has pretty clear plans to make thunderbolt the external PCI bus of the future. Don't forget optical cable versions are coming at some point too.



    Anyway, tech prophecy- or any prophecy for that matter- is a tough industry i would like to stay out of. But it sure would be great if master hackintoshers could figure out how to make the TB ports work like they do on apple gear!



    Thunderbolt certainly does have serious tech potential but everything I have read indicates that outside of the apple/intel agreement it's not cost effective for other vendors to implement due to intels licensing costs being way too high. This is based on my own limited reading so I may be wrong and happy to admit to it if that is the case.


    The problem I foresee is that the hackintosh world will never get to grips with thunderbolt because it's just not likely to crop up on pc motherboards - it's not really the target market. PC's can be upgraded internally for graphics, usb cards, raid cards etc so that's really not what thunderbolt is aimed at - its aimed at closed systems with external only upgrades such as the new mac pro (which came first chicken or egg?).

    Sorry for going off topic btw :)

  5. Been watching this thread for a while and am a bit of a loss - Initially I thought it was a brilliant idea but after reading the feedback on this thread I'm left wondering what the benefits are. It seems it's no easier to get this board up and running than most other hack builds, has a price premium, limited choice of processor and no real benefits that I can see.

    I thought the initial idea was a mobo that made it simple to install osx and was as close to genuine mac hardware as possible but it seems that's not the case from the comments on this thread with most users having to use chameleon and install the same way as most hackintoshers by adding kexts etc.


    What am I missing?


  6. My take on this is that Apple are simply trying to add protection to genuine macs by ensuring that no OS specific kexts are tampered with. They don't care about aftermarket or hackintosh specific kexts that are not installed by the OS because they wont affect genuine macs hence they are in the exclusion list (not Apples problem if they wreak havoc etc).

  7. Afternoon folks, here we go again :)


    You will need 3 things in order to build this usb stick successfully..

    Ok Moving on..

    • First step (pretty obvious) Boot into Snow Leopard, Lion or Mountain Lion
    • Use disk utility to format your USB stick or drive as mac os extended with GUID partition table
    • double click your Mavericks DP1.dmg image if that's what you have, open the image and extract the 'Install OS X 10.9 Developer Preview.app' to your desktop (if you already have the app file you can skip this obviously)
    • Right click the 'Install OS X Developer Preview.app' from your desktop and select 'Show Package contents'
    • Run ShowAllFiles (to show hidden files),
    • Open 'Contents/SharedSupport' and double click 'InstallESD.dmg'
    • right click on the hidden 'BaseSystem.dmg' and select 'open with disk utility',
    • In disk utility look to the bottom left to find 'BaseSystem.dmg', right click it and select 'Restore',
    • Drag your formatted USB stick or drive into the 'destination' box, untick 'erase destination' and click 'Restore',
    • Go for a beer, coffee or whatever takes your fancy as this will take a while!
    • Once restore is complete go to the system, installation folder on the usb stick or drive and delete the 'Packages' alias
    • right click your 'Install OS X Developer Preview.app' from your desktop and select 'Show Package contents' and open 'Contents/SharedSupport'
    • Open the InstallESD.dmg and copy the 'Packages' folder to your usb stick or drive to replace the alias that you deleted in step 11,
    • WAIT for Step 13 to complete and then run the downloaded 'P8P67 Pro USB Installer' package and select your usb drive as the target - this will make the drive bootable and install everything onto the drive to allow you to install on your P8P67 Pro
    • Congratulations your USB stick or drive should now be bootable and allow you to install Mavericks.
    • Boot from the newly created installation USB stick and run the installer (use F8 after post to select the USB stick, let it run the installer and install as usual)
    • Once installation is complete reboot and again boot from the usb stick (F8 after post again to select it as the boot device), When chameleon loads this time you need to select your freshly installed Mavericks hdd to boot from so select it and wait for it to load
    • After Mavericks has booted to the desktop run the installation package that you will find on the root of your USB drive named 'P8P67 Pro Driver Installer.pkg' this will install the bootloader and necessary kexts to your newly installed drive - this should make your new installation bootable.

    Please Note..

    • The installer does not install USB 3, NullCPUPowerManagement or Audio kexts - If you need to sinatll these then the kexts and kextutility can be found in the 'Additional Kexts' folder on the root of your USB drive. I do not use these kexts as I use USB Audio and have a patched bios so I don't need NullCPUPowermanagement - if you need them then install them. 
    • I have not tested the AppleHDA.kext - it's the same one used in Mountain Lion so 'should' work, I'm currently using an X-FI HD USB card which works via spdif.
    • By default the package sets the smbios to use a MacBook Pro 8.3 definition - this is purely to simplify the installation. If you decide to change this to Mac Pro definition then be aware that you will need to delete the AppleTYMCE kext prior to booting after each DP update otherwise you will get a kernel panic.

    As always good luck!!! 

  8. Hi everyone,


    I know i'm not dumb but, I follow all this tutorial, but something was wrong with my config (Asus P8P67 Pro revB3 bios 3207, 16 GB, GTX670 Stock). When I want to boot with andy's bootcd or regae's bootcd nothing happen, until the computer reboot itself at all time.

    Anyone have an idea to solve this problem ?





    I suspect it's an issue with that bios version - i did recommend NOT using a 3000 series bios

  9. I installed 10.8.2 on my today because 10.8 was to buggy. After installation i was not able to make my sound work ( being detected) anymore.


    What did you replace the AppleHDA.kext with? I tried to use the one of my 10.8 installation but it did not have any effect. (everything else works fine.)


    Thanks for your help


    Just run the package again - sometimes the sound wont stick on the the first run.

  10. Andy,


    Massive thanks as usual for your work. However you should be aware that your latest package is not patched for MBR partitions, and I had to manually patch the OSInstall framework and replace OSInstall.mpkg to make the installer work on my hybrid MBR/GUI partition.




    Yup, I figured it's easy enough for people to lookup if they want to install to mbr. Including that patch limits the usefullness of the usb installer for future versions so I decided not to include it.

  11. The board also features an ASMedia ASM1042 for 2 additional ports, but without the suitable kext, it shouldn't be recognized by the OS. When I plug in a USB flash drive or hard drive, the LED of the drive is on, but it doesn't get recognized by the system, it just simply does nothing. I tried the rear and the front ports. Has anybody a hint how I can get this to work? If somebody needs to take a look at the DSDT or ioreg, I've attached them to this post.


    Thanks in advance for your help!




    Try these modified drivers http://www.mediafire.com/download.php?dxcetph021ft8uy

  12. Any reports if the nvidia gtx 670 will work with your P8P67 install?


    Or maybe 660Ti is better value. The 570 is good price too but buying old tech then.


    Found this in the 6970 reports netkas forum so if this is correct guess I answered my own question. Search is my friend!






    570 definitely works (I'm using one) also using a 480 in my spare hack without issue. The 670, 680 and 690 are all definitely reported as working (I don't have any of those cards so have not tested for myself but I trust the reports over at netkas forums indicating that they do indeed work with ML). I can't recall seeing anything about the 660's though so you may want to double and tripple check before buying one.

  13. Word of warning if you are using an OCZ SSD drive to install to....


    It probably wont work, the install will go fine but after rebooting you will just get a grey screen and not reach the desktop. This appears to be a known issue affecting certain SSD's with Mountain Lion (it happens on my cheap {censored} OCZ Petrol drive).


    So if you are using an OCZ SSD stick with Lion for now until a fix appears!